x402 · PRODUCTION + SANDBOX

Market data, paid per request

No TickerLayer account. No API key at the gateway. Your agent asks for a REST resource, sees the exact USDC price, authorizes it, and receives validated market data. Build in the isolated sandbox, then point the same integration at Base mainnet.

Choose a networkIntegration exampleCompare with MCP
  • 41 REST resources
  • Base mainnet
  • USDC
  • Separate Sepolia sandbox
  • HTTP only
41approved resources
$0.01light calls start at
25bulk item cap
6USDC decimals
2isolated network surfaces

NETWORK SURFACES

Production and testing stay separate

Mainnet is the production destination. Base Sepolia is an independent sandbox for test wallets and test USDC. Readiness below is confirmed only from each gateway's public status response.

A readiness result describes gateway health at the time checked; it is not a promise of uninterrupted availability or a substitute for inspecting the signed 402 requirement before paying.

HOW IT WORKS

HTTP payment without a billing integration

The gateway keeps payment logic outside the existing market-data API and settles only after a valid response is prepared.

  1. 01Agent requests data

    A normal GET request targets one approved production or sandbox resource.

  2. 02Gateway quotes the call

    The 402 response declares the network, asset and exact price.

  3. 03Agent authorizes

    The client checks the requirement, signs it and retries the same URL.

  4. 04Data returns

    TickerLayer validates and prepares the response before settlement.

CATALOG EXPLORER

41 focused REST resources

Six repeatable resource types cover the main asset families. Bonds and four market-calendar calls complete the catalog without adding a heavy client-side explorer.

StocksUS:AAPL · TR:THYAO
  • /v1/stocks/symbols
  • /v1/stocks/quote/:symbol
  • /v1/stocks/trade/last/:symbol
  • /v1/stocks/snapshot/:symbol
  • /v1/stocks/agg/:symbol/prev
  • /v1/stocks/agg/:symbol/…
ForexEURUSD
  • /v1/forex/symbols
  • /v1/forex/quote/:symbol
  • /v1/forex/trade/last/:symbol
  • /v1/forex/snapshot/:symbol
  • /v1/forex/agg/:symbol/prev
  • /v1/forex/agg/:symbol/…
CryptoBTCUSD
  • /v1/crypto/symbols
  • /v1/crypto/quote/:symbol
  • /v1/crypto/trade/last/:symbol
  • /v1/crypto/snapshot/:symbol
  • /v1/crypto/agg/:symbol/prev
  • /v1/crypto/agg/:symbol/…
IndicesUS500
  • /v1/indices/symbols
  • /v1/indices/quote/:symbol
  • /v1/indices/trade/last/:symbol
  • /v1/indices/snapshot/:symbol
  • /v1/indices/agg/:symbol/prev
  • /v1/indices/agg/:symbol/…
ETFsSPY
  • /v1/etfs/symbols
  • /v1/etfs/quote/:symbol
  • /v1/etfs/trade/last/:symbol
  • /v1/etfs/snapshot/:symbol
  • /v1/etfs/agg/:symbol/prev
  • /v1/etfs/agg/:symbol/…
CommoditiesXAUUSD
  • /v1/commodities/symbols
  • /v1/commodities/quote/:symbol
  • /v1/commodities/trade/last/:symbol
  • /v1/commodities/snapshot/:symbol
  • /v1/commodities/agg/:symbol/prev
  • /v1/commodities/agg/:symbol/…
BondsUS:10Y · DE:10Y
  • /v1/bond/last/:symbol
Marketsstatus · sessions
  • /v1/markets/status
  • /v1/markets/status/bulk
  • /v1/markets/sessions
  • /v1/markets/holidays
STOCK SYMBOL CONTRACT

Country or market code stays attached.

Stock routes require MARKET:SYMBOL. Use US:AAPL, TR:THYAO, DE:BMW, HK:0700, KR:005930, JP:7203, TW:2330 or CN:600036 — never a bare stock ticker.

AGENT INTEGRATION

Inspect first, authorize second

The cURL examples intentionally return the signed 402 challenge. The Node.js example checks the network and caps a payment at 100,000 atomic units ($0.10 USDC) before the x402 client retries automatically.

curl --include --request GET \
  'https://x402.tickerlayer.com/v1/stocks/quote/US:AAPL'

Production: use eip155:8453 and a dedicated, limited-funds server-side wallet.

Sandbox: set X402_BASE_URL=https://x402-testnet.tickerlayer.com and X402_NETWORK=eip155:84532 with a test-only wallet.

Never: ship a private key in browser code, logs, source control or a chat message.

DETERMINISTIC PRICING

The price is known before authorization

Amounts use integer micro-USDC inside the gateway. Admin controls can update an endpoint without changing payment precision.

Quote · last trade · previous · bond · market status · sessions$0.01
Snapshot · symbol discovery · market holidays$0.02
Historical · 1–100 bars$0.03
Historical · 101–500 bars$0.05
Historical · 501–1,000 bars$0.10
Bulk market status · first item + each additional item$0.01 + $0.002

Bulk requests are capped at 25 items and $0.058 USDC. Sandbox amounts use test USDC. Admin overrides appear in each gateway's public /catalog; the 402 payment requirement returned for the exact request remains the authoritative price.

PAYMENT SAFETY

Prepared first. Settled second.

The payment lifecycle is deliberately narrow, cached and operator-controlled.

01

Invalid calls do not settle

Bad parameters, upstream failures, invalid JSON and empty data stop before settlement.

02

Retries are idempotent

The payment identifier and authorization are bound to one canonical request and prepared response.

03

Limits stay light

Per-endpoint rate limits, short caches, bounded concurrency and response caps protect the core API.

04

Operators stay in control

Routes can be unpublished or disabled, and mainnet can move from a narrow canary to the full catalog deliberately.

TickerLayer provides derived, indicative, non-exchange-sourced market data for informational and technical use. x402 is a payment and access mechanism, not a broker, exchange or execution venue.

X402 FAQ

Questions agents and teams ask first

Two isolated networks, one focused HTTP catalog and an exact price before every authorization.

What is x402?

x402 is an HTTP payment protocol built around the standard 402 Payment Required response. A client requests a resource, receives an exact payment requirement, authorizes it, and retries the same request with payment proof.

Do I need a TickerLayer account or API key?

Not for the x402 gateway. The payment authorization replaces account and API-key authentication for the paid resource. The existing MCP and standard REST products continue to use their current API-key model.

Which network and payment asset are used?

Production uses USDC on Base mainnet. A separate sandbox uses test USDC on Base Sepolia, so developers can validate their integration without mixing test payments with production traffic.

How do I know whether a gateway is operational?

The production and sandbox cards on this page read each gateway's public /ready response. Gateway ready means that readiness check passed; launch configured means the service answered but is not ready; status unavailable means no current readiness result could be confirmed.

What happens when a data call fails?

The gateway validates the route, parameters and returned data before settlement. Malformed, failed, oversized or empty-data responses are not settled.

Can the same payment be charged twice?

Payment identifiers are bound to the exact request and authorization. A completed retry for the same request returns the stored response; using the identifier for a different request or authorization is rejected.

Does x402 include WebSocket streaming?

No. The x402 surface is intentionally REST-only. Use the existing TickerLayer products and entitlements for ongoing WebSocket workloads.

Which asset classes are supported?

Stocks, forex, crypto, indices, ETFs and commodities each expose six resource types. Government bond yields and four market-calendar resources complete the 41-resource catalog.

When should I use MCP instead?

Use MCP for recurring authenticated agent workflows, typed tool discovery and existing plan entitlements. x402 is designed for occasional or autonomous HTTP calls paid per request.

What should I use for high-volume access?

For sustained workloads, predictable quotas or WebSocket access, use a standard TickerLayer plan or contact the team about an enterprise integration.

PRODUCTION + SANDBOX

Build safely, then switch networks.

Start with the Base Sepolia sandbox, verify the 402 requirement and your spending policy, then change the gateway and network together for Base mainnet.

View examplesBack to AI & Agents