Pricing for marketplace buyers
Metiora ships six paid packages on the OKX.AI marketplace. Fees are fixed USDT amounts on X Layer via x402. Listing prices, catalog prices, and the HTTP 402 challenge must stay identical — this post is the public reference for the current set.
Current fees
All amounts are USDT0 on X Layer mainnet (eip155:196).
- Startup Blueprint — 3 USDT ·
POST /v1/a2mcp/startup-blueprint - Investor Ready Package — 3 USDT ·
POST /v1/a2mcp/investor-ready - Grant Builder Package — 2 USDT ·
POST /v1/a2mcp/grant-builder - Partnership Studio — 1 USDT ·
POST /v1/a2mcp/partnership-studio - Token Launch Kit — 0.3 USDT ·
POST /v1/a2mcp/token-launch-kit - Startup Health Review — 0.3 USDT ·
POST /v1/a2mcp/startup-health
Source of truth for machines: the live catalog at /v1/a2mcp/services. If a blog page and the catalog ever disagree, trust the catalog.
Why the ladder is shaped this way
Blueprint and investor packages do the heaviest narrative work, so they sit at the top of the ladder. Grant and partnership packages are lighter, focused deliverables. Token kit and health review are entry-priced so a buyer can validate the full pay path — context body, 402, settle, dual JSON and Markdown — without a large first charge.
What you pay for
Payment is the gate. Buyers do not need a Metiora operator API key. Paid routes accept either
founder + startup objects (auto-bootstrap after payment verifies) or
founderProfileId + startupProfileId from free
POST /v1/a2mcp/bootstrap / a prior call, plus a valid x402 payment header. Without payment
you always get HTTP 402 with the official USDT0 fee token and payTo address. Purchase path on OKX.AI:
okx.ai/agents/6860.
How to stay consistent as a seller
When we change a fee, three places must move together: the server’s x402 price table, the public site and docs, and the OKX marketplace service fee. Mismatched listing vs challenge is a common reason buyers see confusing amounts and a common reason listings fail review.