Skip to content
route402.dev

walletAgentic payments with hard limits

Let the agent pay. Keep the authority.

A remote MCP wallet for paid APIs. The agent can discover, inspect, and estimate freely; your policy decides whether it may sign.

remote MCP · x402 v2 · settles on Flare · no local install

Product preview · example policy

Standing authority

enforced

spent today

$2.40 / $10.00

daily budget
$7.60 remaining
call $0.50
session $5.00
hard stop
Known service · $0.0010allowed
Above $0.25ask owner
Unknown counterpartyblocked

Connection

one MCP URL

Surface

6 tools · 1 spends

Enforcement

before signature

Control

revoke any time

Autonomy should be scoped, observable, and reversible.

policy → signature → receipt

The wallet is the boundary

Give it a budget. Never give it your judgment.

Prompt instructions are not a security boundary. route402 evaluates every paid call against policy stored outside the agent’s context.

Hard money limits

Per-call, session, daily, service, and lifetime ceilings bind independently. The tightest limit wins.

Default-deny trust

Unknown services can stay blocked until their age, reliability, or allowlist entry clears policy.

Human thresholds

Ask for approval above a number you choose. If the client cannot ask, the wallet refuses.

Immediate revocation

Freeze the wallet or revoke one agent grant without changing prompts or waiting for a session to end.

A deliberately small surface

Explore for free. Spend through one door.

Five read-only tools help the agent find the right service and understand the cost. Only call_service can move money.

01

Discover

search · describe

Find capabilities, schemas, prices, and trust evidence across the public registry.

02

Plan

estimate · balance · history

Know the exact price and remaining policy budget before committing to a request.

03

Pay + call

call_service

Evaluate policy, sign the x402 retry, return the API result, and attach the receipt.

Designed for a hostile prompt

A compromised agent still hits the same stop.

Limits live with the signer, not in the prompt. A loop, injection, or tool mistake cannot raise them.

01Layered capsCall, session, day, counterparty, lifetime.
02Anomaly brakeBurst loops and brand-new endpoints slow or stop.
03Allowlists + blocksTrust scope is explicit and inspectable.
04Auditable receiptsEvery paid call returns its result and payment summary.

Remote MCP

One URL. Your existing agent.

Paste the connector into an MCP-compatible client. OAuth keeps connection consent separate from spending authority.

  1. 01CreateSign in, choose a network, and create the wallet.
  2. 02BoundSet hard ceilings, trust rules, and approval thresholds.
  3. 03ConnectPaste one MCP URL and approve the exact scope.
  4. 04ObserveReview grants, spend, and receipts in the authenticated app.

route402 agent wallet

Give the agent room to work—not room to overspend.