Track spending
You can follow what your agent wallets hold and what they spend from the dashboard, from a CSV export, from the agent itself and through the API. What counts as a payment and how it is recorded is explained in Payment intents; the limits that stop spending are in Control spending.
From the dashboard
Balances and the state of each agent
The Agent Wallets list shows, for each wallet, its operators, its balance, its runway, what it spent this month and its status. The runway is the balance divided by the wallet's average daily spend over the last seven days, or over thirty days when the last seven are empty. The dashboard home adds the amount held by all the agents, a curve of that amount over time (one snapshot per day, 90 days by default), the latest payments and what waits for your decision in the Inbox.
The balance is read from an indexer that lags the blockchain by a few seconds. A refresh control next to the balance fetches fresh data.
History and statistics
Expense tracking shows the payments of an application's agent wallets, newest first:
- the totals of the current month: spend, number of transactions and average transaction amount, in your display currency;
- a table with one row per USDC transfer: the agent, its operators, the destination (the service for an x402 payment, the address for a transfer), the amount, the status and the date;
- a detail view of a row, with the on-chain amount, the transaction hash and how the payment was approved: by a named person, or automatically within the spending rules;
- filters by operator, by destination and, once the application has a mission, by mission.
Only the canonical USDC contract is counted. Any other token, and the native coin, is left out of the totals and the history, so an airdropped lookalike token never shows up. A payment that Keyban covered from the welcome offer is flagged as sponsored, and the offer itself appears once at its grant date as a row without an amount, left out of the totals.
Export to CSV
The Export CSV button downloads the transfers of a date range: this month, last month, the last 30 or 90 days, or a custom range. The export honours the operator, destination and mission filters, and holds one row per transfer. Its columns include the date in UTC, the direction, the wallet, the operators, the destination, the amount in the display currency and on the blockchain, the token, the transaction hash, the intent identifier, whether the payment was sponsored, the funding source, and the identity and tax details of your organization. A range that matches more than 50,000 transfers is refused: narrow the range.
Reading the history and exporting it needs read access on agent wallets, which Viewers have. For a read-only access outside the dashboard, such as a supervision tool, a read-only follower key can be minted for a wallet (the admin tool create_wallet_follower_key).
What the agent can do
The agent sees the same figures through two read-only tools. They cannot move funds.
| Tool | What it returns |
|---|---|
expense_stats | The current-month summary for the application's agent wallets: total spent, number of transactions, average ticket, display currency and excluded assets. It can be narrowed to one wallet or one operator. |
list_expense_transactions | The transfers, newest first, with pagination (page and page size from 1 to 100). A row that was not paid from the wallet, such as one covered by the welcome offer, says who covered it. |
The agent also has balance for what the wallet holds now. When the user asks what was spent, or for the transaction hash of a transfer, the agent calls these tools rather than answering from memory. They are listed on the Wallet MCP tools page.
An assistant using the admin tools of the Keyban MCP server, after keyban admin login, can read get_wallet_balance and list_wallet_payments, and the policy history with list_wallet_payment_history. See the Admin tools. The expense endpoints, including the CSV export, are in the Backend OpenAPI reference.
Webhooks
Keyban can push events to your systems with outgoing webhooks. An endpoint is an HTTPS URL registered on an application, with the event types it subscribes to. Each delivery is signed following the Standard Webhooks specification: the secret is shown once when you create or rotate the endpoint, and the receiver checks the webhook-signature header with it. You manage the endpoints through the API or the admin tools (keyban admin commands, or the Keyban MCP server after keyban admin login), which have create_webhook_endpoint, list_webhook_endpoints, update_webhook_endpoint, delete_webhook_endpoint and rotate_webhook_secret.
The events that exist today are the three Digital Product Passport events: dpp.passport.created, dpp.passport.updated and dpp.passport.published. Keyban does not send an event for a payment, a held approval, a top-up or an emergency stop. To follow agent spending, use the dashboard, the CSV export, the agent's tools or the API.
Limits
- The history and the totals count USDC transfers only.
- The balance and the history come from an indexer and can trail the blockchain by a few seconds.
- A CSV export is capped at 50,000 transfers and needs a date range.
- A signed x402 payment that never settles is retired to
failedwhen the expense figures are read, which releases the budget it held. A figure can therefore change slightly between two reads. - Keyban e-mails people when a monthly budget (the organization's, an application's, a free share, or the monthly budget of a wallet whose application has a budget) is on pace to run out and when it is used up; other alerts to a human, such as velocity alerts or alerts when a wallet with no budget above it reaches its limits, are Coming soon. See Control spending.