Define the role before the interface
A market page, account connection and order ticket may look similar across products while the underlying businesses differ. Identify who lists contracts, controls outcomes, holds assets, receives orders and handles settlement. Use those facts to guide architecture and the questions for counsel.
Build coherent player journeys
Plan discovery, market detail, account connection, positions, history and support as one product. Record partner dependencies and the source of market and settlement data. Apparently connects implementation plans with the product facts and documents that legal review needs.
Separate a market from software around a market
Running an exchange and building an independent interface to another venue are different activities. A proposed ISV route should be evaluated against the actual functions, compensation and relationships involved. Federal requirements, state issues and partner restrictions need current analysis rather than a blanket launch claim.
Before you build
Does Apparently operate a prediction-market exchange?
Apparently supplies development and legal-workflow software. It is not presented as an exchange, broker, custodian or source of execution.
Where should an independent software vendor start?
Define the proposed venue relationship, user account and order flows, custody boundaries and compensation, then review those facts. The ISV guide focuses on this software-provider structure.
Two roles, one connected workflow
Apparently AI provides the coding and planning workflow. Apparently Law advises on prediction markets under a separate engagement. Counsel reviews the facts and signs any opinion; payment processors make their own approval decisions.
For payment processors · Meet Kale Pasch and Mandy Pasch · Pricing
Product guide updated 2026-10-31. This page describes scope and questions for review; it is not jurisdiction-specific legal advice or an approval.