Start Build or Pro access via x402 USDC payment
0xArchive API reference for Start Build or Pro access via x402 USDC payment. Includes route metadata, schemas, examples, and implementation notes.
payment-signature header required by this operation instead of X-API-Key. See wallet access and x402, then review REST authentication exceptions.Machine schema
Machine schema
Headers
Base64-encoded x402 v2 payment payload containing the EIP-3009 signed USDC transfer authorization. Omit on first request to receive payment details.
Selects the 2026-10 response contract. Send 2026-10-01; any dated version on or after it selects the same shapes. Without the header every response keeps its existing shape. With it:
- The data quality routes,
/v1/status/coverageand/v1/symbolsanswer the standard{success, data, meta}envelope. - Record times that are integer milliseconds by default become RFC 3339 UTC strings with millisecond precision, and the integer moves to a
*_msfield: L4 resting-ordertimestamp(timestamp_ms), CVD buckets, HIP-3 oracle reads, Lighter and Lighter on Robinhood Chain liquidations and liquidation volume. Levels and trigger-levelssnapshot_tsbecome RFC 3339 withsnapshot_ts_ms. - Error bodies carry the contract
error_codenames:invalid_parameterinstead ofinvalid_query_paramsandinvalid_path_params,historical_depth_exceededinstead ofhistory_window_exceeded, andhistorical_range_exceededinstead ofrequest_range_exceeded; a malformed cursor that fails to parse answers 400invalid_cursorinstead ofinvalid_query_params. With0xArchive-Version: 2026-10-01, malformed cursors on trades, liquidations, L2 and L4 diffs, order history, TP/SL and order-flow routes answer 400invalid_cursor. Without the header, the first six route families treat a malformed cursor as no cursor and return the first page; order flow answers 400invalid_query_params. Malformed trade time inputs answer 400invalid_time_rangewith the header and 400invalid_query_paramswithout it.
The response echoes the selected version in its own 0xArchive-Version header.
2026-10-01 "2026-10-01"
Body
Subscription tier to purchase
build, pro "build"
Response
Subscription created successfully (returned when valid payment-signature header is provided)
The generated API key for the new subscription
"0xa_..."
The subscription tier activated
"build"
Subscription expiration date (30 days from purchase)
The wallet address associated with the subscription
On-chain transaction hash for the USDC transfer (if settled)