Wallet and Payment Rails
AgentRouter gives the agent one wallet and one routed execution surface.
Under the hood, supply routes can still use different settlement rails such as direct API billing, x402, and MPP through Tempo.
The point of AgentRouter is that the agent usually does not need to care.
AgentRouter Wallet
AgentRouter bills in credits:
The wallet is the balance you fund and monitor in AgentRouter.
Read the current balance:
Read recent usage:
What x402 Is
x402 is a payment rail used by some paid API supply routes.
In AgentRouter, that matters at the route layer, not at the capability layer.
You may see route metadata such as:
networkKey: "agentcash"settlementRail: "x402"
For the agent, the important point is:
- you still call AgentRouter through one auth model
- AgentRouter handles the supply-side settlement path where possible
What MPP And Tempo Mean
MPP is another supply-side settlement path.
In the current AgentRouter implementation, some routes are modeled as:
networkKey: "mpp"settlementRail: "mpp"
AgentRouter then handles the Tempo-backed settlement mechanics for those routes.
Again, the agent should not need to understand the low-level payment handshake to decide which capability it wants.
Why This Abstraction Matters
Without AgentRouter, an agent has to care about:
- which provider uses direct API keys
- which provider expects x402
- which route is on MPP
- whether the cheapest route is even executable right now
With AgentRouter, the agent usually just needs to care about:
- the capability
- whether to recommend first
- whether to execute now
Reading Route Metadata
If you do want to inspect the settlement path, list the routes:
Look for fields such as:
networkKeyrouteModesettlementRailstartingCostCreditsstatus
Practical Rule
The agent should optimize for capability intent.
AgentRouter should absorb the complexity of x402, Tempo, and other settlement differences unless a workflow explicitly requires BYO resources or an owned wallet.