Skip to main content
The Agent Gateway sits in front of your HTTP API and enforces per-request USDC payments using the x402 protocol. When an AI agent calls your route without a valid payment, the gateway immediately returns a 402 response describing exactly what is owed. The agent pays autonomously, retries the request with the payment header attached, and the gateway proxies the request to your upstream service after verifying settlement on-chain. You collect USDC directly to your organization’s receiver wallet — no invoicing, no subscription management required.

​
Environments

Use the sandbox URL during development and agent testing. Switch to the production URL when you are ready to accept live USDC payments.
The sandbox route is publicly accessible. Any unauthenticated GET to it returns a real 402 response with payment requirements — useful for testing client-side x402 handling without creating an account.

​
Route URL pattern

Every route you create is reachable at a predictable URL derived from your organization slug and the route path you configure:
For example, if your organization slug is acme and you create a route at path /summarize, agents call:

​
Core paths

​
Learn more

Payment Flow

Understand the full x402 request lifecycle, headers, and error codes your agent will encounter.

Routes

Create and manage routes from the dashboard or the management API.

MCP

Expose your gateway routes as MCP tools for Claude and other AI assistants.