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

9–12 months · partial · qualification live

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 a settlement-layer TODO and is not implemented on this page.

Reputation
Operations
Proof
External supply wins
Payouts
TODO

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%

TODO(settlement) — revenue share, Stripe Connect, and wallet payouts are not wired.

Score the work, delay the payout

Qualification only. Observed seller ops replace fixtures after five inspected receipts. No seller USDC, Connect, or revenue share.

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

    Leave revenue share unwired

    TODO(settlement): do not pay sellers, split charges, or attach Stripe Connect from this surface. The take-rate discussion in the strategy is illustrative only.

  • 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.

  • PayoutsTODO

    Revenue share, Stripe, and wallet settlement are not live here.

This page does not charge.

Stripe Checkout, wallet env, and seller payouts stay off this page. Authenticated outcomes execute is the live charge path. Named-model MCP and /ai-router remain available.

  • TODO(settlement)

    Do not grant credits, settle USDC, or pay seller revenue share from this surface.

  • TODO(stripe)

    Do not wire Stripe Checkout, card forms, or human top-up URLs on these plan pages. Settlement stays a later integration.

  • TODO(x402-env)

    Do not read X402_EVM_PRIVATE_KEY or OFFLINECREATOR_X402_MAX_USD here. Wallet settlement stays on the live /x402 runbooks.

Continue the plan

Plan FAQ

Will I be paid if my capability is routed?

Not from this page. Revenue share is a planned settlement-layer concern. Stripe, Connect, x402 seller payouts, and credit grants are all TODOs.

Are the reputation numbers real?

Seed fixtures stay illustrative until five inspected receipts exist for that seller. Then scoreSeller source is observed. Payouts stay false.

Score first. Pay later.

If external supply cannot win on operations, a take rate is irrelevant. Payouts stay a TODO.

Back to the 12-month plan