Niches · Agent wallets & spending controls
Pay an x402 or MPP API from the agent's own wallet
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The wallet signs the payment for the asset and network the seller asks for, inside the caps, the request is retried and returns 2xx, and the payment shows in the wallet history with its transaction reference, through a CLI, SDK or MCP tool the docs name.
How agents ask for it: pay for this API call from my agent wallet
, use the wallet to get the paid result
, call this x402 endpoint
Does the job, with a limit 9
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Circle Wallets (Agent Wallets, Programmable Wallets) BB Circle Technology Services, LLC | circle services pay takes method, body, chain and --max-amount, and the overview says limits cover x402 payments. Whether a nanopayment appears in circle transaction list with a reference is not stated, and policies work on mainnet only. source |
| Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) BB Coinbase, Inc. | awal x402 pay takes method, body and --max-amount for USDC on Base, and Wallet MCP pays exact, upto and auth-capture schemes. The pay reference shows no transaction reference in its output, and AgentKit still has no x402 action (acc-12, open). source |
| FluxA AI Wallet E FluxA Technology Pte. Ltd. | fluxa-wallet x402 signs x402 v1 and v2 payloads inside a signed mandate and returns the retry header, refusing with mandate_budget_exceeded. The agent replays the request itself, payments are USDC on Base, and an open issue reports wrong units and error codes across CLI, skill and MCP (acc-17). source |
| Kite Agent Passport D Datalego Inc. | agent:session execute pays x402 with method, headers and body, parses multi-offer 402s, returns decline reasons, and activity filters by merchant and date. The changelog says hosts outside the allowlisted catalogue need manual allowlisting, and a transaction reference in the result is not shown. source |
| Openfort BB Alamas Labs Inc. | The x402 recipe builds an app whose backend wallet signs EIP-3009 authorisations or sponsored USDC transfers on Base with an X402_MAX_AMOUNT setting. It is a sample app rather than a pay command, and typed-data signing is evaluated as a raw hash (acc-15, open). source |
| Privy Wallets (server wallets, agent wallets, policy engine) BB Horkos, LLC | The agent wallets page points to x402 and MPP recipes and the Agent Wallet Sandbox CLI pays both, but the recipes were not opened, so per-payment caps on the MPP path and a transaction reference in history are not confirmed here. source |
| Agent Vault by Self D SocialConnect Labs, Inc., doing business as Self Labs | pay_request pays x402 services sold on Buy from an owner-funded wallet under the agent cards' limits and merchant lists, with Agent Vault holding the key. It is a preview, reaches only Buy's catalogue, and runs on Celo Sepolia until mainnet is cleared. source |
| Sponge Wallet F Sponge Inc. | The README claims x402 and MPP support and shows pay discover and pay service commands; the parameters, per-payment maximum and payment history were in the refused docs. source |
| Turnkey Agentic Wallets BB Turnkey Global, Inc. | @turnkey/viem plugs a policy-checked signer into the stock x402 fetch wrapper and mppx client, which parse the 402, sign and retry. Caps come from policies on the EIP-712 or transaction fields rather than a pay command maximum, and no payment history with reference is described. source |
Doesn't do this job 2
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Agentcard C Agentcard Corporation | No x402 or MPP payment in the docs index; Agentcard pays card checkouts only. source |
| Yield.xyz MCP server BB Omni Ltd. (Yield.xyz) | It charges x402 per call over quota as a seller; it does not pay other services from a wallet. source |
What stops agents finishing
- wallet holds USDC on a different network than the seller accepts
- client approves every payment by default unless a cap is set
Around it
Before: pay-per-call.discover-payable-service, agent-wallets.fund-and-cap. After: pay-per-call.settle-and-prove.
Where this comes from
Weight 14 of 100 in Agent wallets & spending controls: 3 of 20 accounts (acc-04, acc-12, acc-18); most x402 payment accounts sit in the pay-per-call map, so this is lower here
The same as data: /api/v1/use-cases/agent-wallets.pay-per-call-from-wallet.json, or the MCP tool get_use_case with id agent-wallets.pay-per-call-from-wallet. Other jobs in this category: /api/v1/niches?category=agent-wallets.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.