Niches · Agent wallets & spending controls
Give an agent money to spend under limits a person sets
Four or more companies' docs show a full fit.
What counts as done
A wallet or card exists that the agent can use, funded from a source the person controls, with per-transaction and per-period caps enforced by the service (not the prompt), and the person can read the remaining balance and caps.
Measured, for our own tests: an attempt above the cap is refused in a test. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: give my agent 20 dollars to spend this week
, set up a wallet for my agent with a daily limit
, make a card my agent can use, capped at 50
, top up the agent budget
Does the job 4
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| Circle Wallets (Agent Wallets, Programmable Wallets) BB Circle Technology Services, LLC | circle wallet limit set takes per-transaction, daily, weekly and monthly USDC caps over a rolling window, enforced by Circle per chain with a 100 USDC monthly default; limit budget shows what remains, and keys are 2-of-2 MPC with the user holding custody. source |
| Kite Agent Passport D Datalego Inc. | kpass agent:session create sets --max-amount-per-tx, --max-total-amount and --ttl, the person approves the session, and the server enforces the caps (a changelog fix covers per-transaction routing caps with merchant costs); funding is USDC.e by card, deposit or bridge. source |
| Privy Wallets (server wallets, agent wallets, policy engine) BB Horkos, LLC | Policies run in the enclave before signing, default-deny, and aggregations add spending caps over rolling windows next to per-transaction caps and recipient allowlists; users fund by card, bank transfer or stablecoins and can revoke delegated access. source |
| Agent Vault by Self D SocialConnect Labs, Inc., doing business as Self Labs | An agent card over the holder's own card sets a per-transaction cap, rolling daily, weekly and monthly limits, merchant rules and an approval amount, enforced by the proxy at fill, and the dashboard shows spend against caps. Period limits apply on production only; daily needs Plus. source |
Does the job, with a limit 6
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 |
|---|---|
| Agentcard C Agentcard Corporation | A card's amount_cents is its spend limit, single_use closes after one charge and expires_at ends it; funding is the user's balance (Apple Pay or Google Pay, after KYC) or the company's. Caps are a per-card total with no period, and the only merchant lock is AI labs. source |
| Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) BB Coinbase, Inc. | Server wallets take service-side policies (reject wins over accept) with per-transaction value and address rules, and the Agentic Wallet funds from Coinbase Onramp. No per-period cap appears in the policy engine page, and Wallet MCP instead needs a person to approve every write. source |
| FluxA AI Wallet E FluxA Technology Pte. Ltd. | A mandate the user signs in the FluxA Wallet sets a budget limit and time window (default 8 hours) that the wallet enforces, and mandate-status shows what remains. It is one total per mandate, with no per-transaction cap or payee list, and key custody is not stated. source |
| Openfort BB Alamas Labs Inc. | Signing policies are fail-closed with per-transaction value caps and allowlists, but no daily or rolling cap, and a backend send is evaluated only as signEvmHash, so its value and address rules bind only if the caller pre-flights with policies.evaluate. source |
| Sponge Wallet F Sponge Inc. | The SDK README on npm lists spending limits and allowlists and agent-scoped API keys, but docs.paysponge.com disallows Claude in robots.txt, so the cap periods, enforcement point and funding steps could not be read. Vendor claim only. source |
| Turnkey Agentic Wallets BB Turnkey Global, Inc. | An agent gets a non-root user that is default-deny, and enclave-checked policies cap value per transaction and restrict destinations and chains. The docs read cap per signing only, with no daily or weekly window, and funding is the company's own wallet. source |
Doesn't do this job 1
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Yield.xyz MCP server BB Omni Ltd. (Yield.xyz) | Yield.xyz holds no funds and sets no caps; it returns unsigned transactions for the caller's own signer. source |
What stops agents finishing
- a person must sign up, verify email and create a passkey in a browser first
- funding needs the right asset on the right chain, or a card top-up with a minimum
- caps are amounts only, with no payee allow-list
- parallel requests can pass a rolling cap before it updates
Around it
Before: chat.user-request. After: agent-wallets.pay-per-call-from-wallet, agent-wallets.card-checkout, agent-wallets.revoke-and-audit.
Where this comes from
Weight 28 of 100 in Agent wallets & spending controls: 8 of 20 accounts (acc-01, acc-03, acc-05, acc-06, acc-07, acc-18, acc-19, acc-20); the question every HN thread on agent spending opens with
The same as data: /api/v1/use-cases/agent-wallets.fund-and-cap.json, or the MCP tool get_use_case with id agent-wallets.fund-and-cap. 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.