Pricing

x402 prices per call, per asset, and per hour, paid in USDC on Base. Partners with an API key pay nothing per call.

Every paid route is priced in USDC on Base (eip155:8453) and paid with x402. You pay only for calls that succeed: a 400, 422, or 500 never settles.

x402 prices

Capability	REST route	MCP tool	Unit	Price (USDC)	Base units
Optimize	POST /optimizer/{chain_id}/optimize	optimize	per call	0.10	100000
Market list	GET /{chain_id}/{token_address}/protocols	list_protocols	per call	0.005	5000
Health	POST /protocols/health	protocol_health	per asset in the request	0.01	10000
Monitor	POST /monitor/sessions	create_monitor_session	per hour of the window	0.02	20000

USDC has 6 decimals, so 100000 base units is 0.10 USDC. The amount in the 402 offer is always in base units and already holds the total for the request.

Worked examples

Request	Units	Total (USDC)	amount in the offer
One optimize call	1	0.10	100000
Market list for USDC on Base	1	0.005	5000
Health for three assets	3	0.03	30000
Six-hour monitor session	6	0.12	120000
24-hour monitor session (the maximum)	24	0.48	480000

A monitor session is paid up front for the whole window. Closing the socket early does not refund the unused hours, so buy the window you need and renew it when the server sends session_expired.

What is free

• MCP initialize, tools/list, and the tool schemas. Only tools/call is paid.
• The 402 offer itself. Asking for the price costs nothing.
• Every route for partners who send X-Partner-Name and X-Partner-API-Key.

Partner plans

Products that call the API at volume, or hold many monitor sockets, can take a partner key on a monthly plan instead of paying per call. Write to [e-mail].

The live price is the one in the 402 offer you receive. If a price changes between the offer and your retry, the server answers with a new 402 carrying the current price, and nothing is charged.