Roadmap & launch gates

Wallet signatures, persistent accounts, owner-scoped key management, and supplier intake form the foundation. Their tests must remain in place as the interface and execution system evolve. The public waitlist should stay independent of unfinished paid features.

1. Create or obtain an authorized provider account and approve an experiment budget.
2. Deploy or connect one appropriately licensed model endpoint.
3. Test real answers, usage reporting, timeouts, failures, and actual costs.
4. Implement safe provider qualification and catalog publication.
5. Keep the initial catalog narrow until the service is demonstrably reliable.

Implement the ledger, spending limits, reservations, idempotency, and usage reconciliation before accepting funds. Resolve custody and legal/business requirements. A UI that can connect a wallet is not approval to collect customer deposits.

Bring an independent qualified supplier through onboarding, route actual demand under agreed service conditions, record earnings, and complete a reconciled payout. Operator-owned supply can bootstrap the service, but it should not be misrepresented as independent seller participation.

• x402 access once Robinhood-native protocol and facilitator behavior are verified.
• Additional models and modalities after compatibility, rights, cost, and privacy checks.
• Stronger privacy tiers with actual contractual or attested infrastructure.
• Optional knowledge/retrieval features where measured quality and cost justify them.
• Self-service GPU software only after update safety, networking, hardware support, and operations are ready.
• Advanced capacity procurement only if buyers need it; not as a prerequisite for ordinary chat.