How Axo Fits Together
A user-facing mental model for Axo wallets, paywalls, clients, and operator controls.
Axo has a simple split:
@axobot/payprotects routes and returns payment challenges@axobot/fetchandaxo fetchsolve those challenges and retry automatically@axobot/mppxhandles advanced session-based payment flowsaxo.botgives you the product surface for projects, agents, balances, and controls
Mental Model
graph LR
A[Your app or agent] -->|Calls protected API| B[Axo Paywall]
B -->|402 challenge| A
A -->|Pay invoice| C[Agent wallet]
A -->|Retry with proof| B
B -->|Protected response| A
A -->|Operate agents and policies| D[axo.bot]Axo Products
Axo CLI
The fastest way to initialize a wallet and make a paid request.
Axo Fetch
Embed payment-aware fetch flows in your own code.
Axo Pay
Put a paywall in front of your own routes.
Axo MPPX
Use session-based payment primitives for longer-lived flows.
Axo.bot Dashboard
Operate projects, agents, balances, approvals, and policies.
Typical Flow
Protect a route
Use Axo Pay to return a payment challenge instead of a premium response.
Let an agent or app pay
Use axo fetch or @axobot/fetch to detect the challenge, pay it, and retry automatically.
Operate the wallet layer
Use axo.bot to manage the agents doing the spending, along with balances, approvals, and guardrails.
Move to sessions when needed
Use @axobot/mppx when you want session-based access rather than one-off payment proofs.