OfflineCreator Studio
Start creating
AI Router · CLI · MCPCheapest eligible quotes before you create

9–12 months · partial · scoring only

Reputation is operational.

A capability’s score should look like operations, not a star rating: jobs completed, 30-day success rate, median latency, refund rate, regeneration rate, repeat-route rate, and price variance. Observed receipts write those figures back. Paying the seller a revenue share is not implemented.

Reputation
Operations
Proof
External supply wins
Payouts
Not live

Illustrative reputation · not live seller data

  • jobs_completed18,421
  • success_rate_30d98.7%
  • median_latency14s
  • refund_rate0.6%
  • regeneration_rate7.2%
  • repeat_route_rate41.0%
  • price_variance0.0%

Revenue share and payouts to third-party capability sellers are not live.

Score the work, delay the payout

Scoring only. Observed seller ops replace fixtures after five inspected receipts. Pilot routing, seller USDC, Connect, and revenue share are not live.

12-month plan overviewLive AI router
  1. 01

    Publish operational metrics

    jobs_completed, success_rate_30d, median_latency, refund_rate, regeneration_rate, repeat_route_rate, price_variance. Decorative badges are not enough.

  2. 02

    Route only qualified supply

    The router should be able to pick a third-party capability over first-party supply when the numbers win. That is the 12-month proof point.

  3. 03

    Keep spend policy on the buyer

    Autonomous purchasing still needs spend caps, route receipts, and explicit task boundaries. A seller score does not bypass the quote.

  4. 04

    Revenue share is not live

    Third-party capability sellers are not paid, charges are not split, and no Stripe Connect account is attached. No take rate is applied or reported anywhere.

  • ReputationOperations

    Success, latency, refunds, regenerations, reuse — not stars.

  • ProofExternal supply wins

    The year-one test is whether a third-party capability takes real routed traffic.

  • PayoutsNot live

    Revenue share and payouts to third-party capability sellers are not live.

This page does not charge.

This page never opens Stripe Checkout, uses a wallet, or pays sellers. Authenticated outcome execute is the live charge path for agents. Named-model MCP, CLI, and /ai-router remain available.

  • No payouts from this page

    This page does not grant credits, settle USDC, or pay anyone. Revenue share for third-party capability sellers is not live.

  • No card checkout here

    People buy plans and credit packs through Stripe Checkout on /pricing. These plan pages never open Checkout or ask for card details.

  • No wallet payments here

    Agents that pay in USDC over x402 do it from their own wallet through the stdio MCP server or the CLI. These pages never ask for or hold a wallet key. Setup lives on /x402.

Continue the plan

Plan FAQ

Will I be paid if my capability is routed?

Not today. Revenue share for third-party capabilities is planned, not live: there are no Stripe Connect, x402, or credit payouts to capability sellers.

Are the reputation numbers real?

Seed fixtures stay illustrative until five inspected receipts exist for that seller; after that the score uses observed data. Payouts are not live.

Score first. Pay later.

If external supply cannot win on operations, a take rate is irrelevant. Payouts are not live.

Back to the 12-month plan