Pricing for agents
Every read in the catalog is monetized through one of two paths: per-call x402 payment, or a session cookie issued after a Solana wallet signature. Pick whichever fits your traffic. Browser UI users get the cookie path automatically; headless agents choose.
SOL = $83.81 (coinbase, cached up to 10 min).
x402 per-call pricing
Every gated API path returns HTTP 402 with a challenge body unless the caller proves a payment in the X-Payment header. The same flat price applies to every endpoint in x402.gatedPaths on the manifest, including the MCP endpoint.
| Per call | 0.00015 SOL | $0.0126 | 150000 lamports |
Volume economics
Monthly cost (30-day months) at four traffic levels. The break-even against a sign-in session is somewhere in the low thousands of calls per day, depending on traffic burstiness.
| Calls / day | SOL / month | USD / month | Recommended path |
|---|---|---|---|
| 100 | 0.450 | $37.71 | x402 per call |
| 1,000 | 4.500 | $377.14 | x402 per call |
| 10,000 | 45.000 | $3771.45 | SIWS session |
| 100,000 | 450.000 | $37714.50 | SIWS session |
SIWS session bypass — free
Sign once with a Solana wallet, get an HttpOnly cookie that bypasses the gate for an hour. No per-call payment. No subscription. The cookie is HMAC-signed server-side so it can't be forged; spoofing the Origin header does not work.
MCP server
The Streamable HTTP MCP endpoint at /api/mcp is x402-gated like any other read. Each MCP call counts as one x402 call. SIWS sessions cover MCP traffic the same way they cover plain HTTP.
Transaction-producing calls
The build endpoints (every tool that returns an unsigned transaction) also embed a flat lamport fee inside the transaction itself. That fee is separate from the x402 per-call price and applies once the wallet submits the signed tx. See user-facing pricing for the per-op breakdown.
Machine-readable
Both pages render from the same source:
/api/pricing— every fee, with live USD figures/api/manifest— endpoint inventory + x402 config + SIWS endpoints
Build pricing decisions from the JSON; treat this page as the rendered view of it.