Skip to content
route402.dev

402The pay-per-call internet

An API network that pays as it goes.

Agents discover an endpoint, pay the exact price, and get the response in one HTTP exchange. API teams get paid for every successful call.

List an API Explore the network

A live paid request

No checkout. No API key handoff.

x402 v2
the exchangelive · 2.4 s end to end
  1. 01GET /x/acme-weather/current?city=Zagrebno payment attached0 ms
  2. 02402 PAYMENT-REQUIREDaccepts: exact · eip155:114 · 1000 atomic$0.0010
  3. 03GET /x/acme-weather/current?city=ZagrebPAYMENT-SIGNATURE: eyJzY2hlbWUiOiJleGFjdCIs…12 ms
  4. 04200 OK{"city":"Zagreb","tempC":21,"sky":"clear"}2.4 s

verify 34 msupstream 198 mssettle 2.1 ssettled $0.0010receipt rct_8f31c2

Protocol

x402 v2

Network

eip155:114

Pricing

exact atomic

Settlement

direct to seller

One request · one price · one signed retry

discover → inspect → pay → receive

Public endpoint directory

Find and pay for an API like calling a function.

Search by capability, compare prices and reliability, then let the wallet enforce policy before it signs. The registry is public; browsing is free.

Search the directory
Example query
Current weather in Zagreb
01public

Discover

Match capability and input schema.

02$0.0010

Inspect

Check price, provenance, and settled activity.

03200 OK

Call

Sign only after wallet policy passes.

Start from either side

Publish an endpoint. Or fund an agent.

For API teams

Sell each successful call.

Keep your upstream exactly as it is. route402 protects the credential, presents the payment terms, and routes paid traffic.

  1. Describe and test the API
  2. Choose an atomic-unit price
  3. Publish to the public registry
Open publisher
For agent owners

Set limits once. Let the agent work.

The wallet can search and estimate freely. Hard per-call and daily limits are checked before any signature leaves it.

  1. Connect the wallet MCP
  2. Set spend and trust policy
  3. Discover, pay, and call
Create a wallet
Flare

Settlement partner

Gas, handled.

Flare x402 facilitator

Settlement gas, sponsored on eligible requests.

route402 uses the Flare x402 Facilitator to cover eligible settlement gas, so an agent can pay for an API call without managing a separate gas balance.

Explore the facilitator

The x402 exchange

Payment belongs inside HTTP.

A 402 response carries exact payment requirements. The client checks policy, signs, retries, and receives the API response.

  1. 01RequestCall a normal HTTP endpoint.
  2. 02PriceReceive exact payment requirements.
  3. 03PolicyCheck trust and limits before signing.
  4. 04ResponseRetry, receive data, and settle.

Trust before spend

Evidence for software that spends money.

Capability searchMatch what an endpoint does, not just what it is called.
Measured signalsKeep observed settlement and reliability distinct from publisher claims.
Sealed credentialsInject upstream secrets at the gateway; never expose them to buyers.
Policy before signatureStop unknown or over-budget calls before money can move.

route402 · built for agents

Two prompts from your first paid request.

Publish an endpoint or fund an agent. No SDK is required to begin.

Publish an API Open wallet
powered byFlare