How it works

Every Invoket endpoint is paid per request over the x402 standard, which reuses the HTTP 402 Payment Required status. No sign-up, no API key, no subscription: an autonomous agent — or a developer with an x402 client — pays each call in stablecoin and gets the response back on the same request.

Pay per call

One call, three steps, no intermediary between you and the gateway.

1 · 402
You call the endpoint; the gateway replies 402 with the price and the accepted payment rails.
2 · Signed payment
Your client (or agent) signs the stablecoin payment and replays the request with the proof.
3 · Response
Once the payment is verified, the gateway runs the call and returns the response.

Ready to wire it up? Follow the quickstart for runnable snippets (curl, x402-fetch, MCP).

Accepted rails

Settle in stablecoin across several networks. Available assets are read live from the catalog.

0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 Base
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v Solana

Details on assets, networks and settlement: payments & rails.

Try before you pay

Some endpoints offer a daily free call, identified by payer address — no account, no coupon. When an endpoint offers a trial, its 402 challenge includes an extra rail at a zero amount: sign it with the same x402 client you already use to pay, replay the call, and it settles for free. Endpoints that currently offer one carry a badge on the endpoint listing and announce it in the catalog.

Mechanism and discovery details: for agents.

You only pay for answers

The gateway settles a payment only when the call actually succeeds — a 2xx response with a usable result. A malformed request, an upstream error or an unanswerable query is never charged: you get the error back and keep your funds. That behavior holds on every endpoint, so an agent can retry or move on without burning its budget on failures.

How agents should handle responses and errors: for agents.