# route402 agent wallet

> A remote MCP server that gives an AI agent a spending-capable wallet, plus a way to find, price, and call any x402 service. Spend limits are enforced inside the wallet, not delegated to the agent's judgement.

MCP endpoint: https://wallet.route402.dev/mcp
Transport: Streamable HTTP. Auth: OAuth 2.1 + PKCE, dynamic client registration, audience-bound tokens.
Scopes: registry:read, wallet:read, wallet:spend — wallet:spend requires its own consent screen showing the limits.

## Docs

- [Quickstart](https://wallet.route402.dev/docs/quickstart.md): Connect the wallet to an MCP client and make your first paid call.
- [Tools](https://wallet.route402.dev/docs/tools.md): The six MCP tools, what each returns, and which one spends.
- [Spend policy](https://wallet.route402.dev/docs/spend-policy.md): The limits that bound what a compromised agent can cost you.
- [Custody](https://wallet.route402.dev/docs/custody.md): Where the key lives, and what that bounds.
- [Configuration](https://wallet.route402.dev/docs/configuration.md): Environment variables, and the one you must set before the wallet can pay for anything.
- [Authorization](https://wallet.route402.dev/docs/oauth.md): OAuth 2.1, PKCE, dynamic registration, and audience-bound tokens.

## Machine-readable

- [Full documentation](https://wallet.route402.dev/llms-full.txt): every page concatenated as plain markdown
- [Protected resource metadata](https://wallet.route402.dev/.well-known/oauth-protected-resource): RFC 9728
- [Authorization server metadata](https://wallet.route402.dev/.well-known/oauth-authorization-server): RFC 8414
- [Health](https://wallet.route402.dev/api/health): service and datastore status

## Copy-pasteable MCP config

```json
{
  "mcpServers": {
    "route402-wallet": {
      "type": "http",
      "url": "https://wallet.route402.dev/mcp"
    }
  }
}
```