Niches · Agent wallets & spending controls
Send a payment and confirm it landed without sending twice
Two or three companies' docs show a full fit.
What counts as done
One transfer is sent on the network the agent asked for, the tool returns its hash even when the receipt lookup fails, and an idempotency key or status lookup lets the agent check before any retry.
How agents ask for it: send 10 USDC to this address
, did the transfer go through
, pay this invoice onchain
Does the job 2
The docs show it meets the test above, and nothing we read says otherwise.
| Listing | Why |
|---|---|
| FluxA AI Wallet E FluxA Technology Pte. Ltd. | fluxa-wallet payout sends USDC on Base with a required --id that doubles as the idempotency key, defaults to the user approving each payout, and payout-status is polled for the txHash. source |
| Turnkey Agentic Wallets BB Turnkey Global, Inc. | Activity submission is idempotent on a fingerprint of the POST body, so resubmitting the same request returns the same activity, and get_activity reports COMPLETED, FAILED, CONSENSUS_NEEDED or PENDING before any retry. 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 |
|---|---|
| Circle Wallets (Agent Wallets, Programmable Wallets) BB Circle Technology Services, LLC | circle wallet transfer takes chain and amount, and transaction list filters by state (sent, confirmed, failed) for a check before retry. Transfer has no idempotency key, unlike swap and bridge, which say a retry without one can duplicate. source |
| Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) BB Coinbase, Inc. | awal send rejects chains other than base, polygon and solana. Open AgentKit issue 1547 reports a sent ERC-20 transfer reported as failed when only the receipt lookup failed, so the agent paid again (acc-09). source |
| Kite Agent Passport D Datalego Inc. | kpass wallet send transfers USDC, and step-up sends show amount, asset and recipient on a passkey page that reports the transaction hash. No idempotency key or status lookup for send appears in the reference. source |
| Openfort BB Alamas Labs Inc. | A backend send returns the receipt's transactionHash and the recipe polls until a hash exists. No idempotency key for sends is documented in the pages read, and a send without a fee sponsorship can sit pending. source |
| Privy Wallets (server wallets, agent wallets, policy engine) BB Horkos, LLC | Idempotency keys hold for 24 hours, a matching body returns the stored response and a changed body returns 400, so a retry is safe. Whether the transfer response carries the hash when the receipt lookup fails was not read. source |
| Sponge Wallet F Sponge Inc. | The CLI shows send with an explicit chain and asset and tx status by chain and hash, so an agent can check before retrying; idempotency for sends was not readable. source |
Doesn't do this job 3
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Agentcard C Agentcard Corporation | No onchain transfers. source |
| Agent Vault by Self D SocialConnect Labs, Inc., doing business as Self Labs | No onchain transfers. source |
| Yield.xyz MCP server BB Omni Ltd. (Yield.xyz) | No transfers; submit_hash only records a hash the caller's signer produced. source |
What stops agents finishing
- tool reports failure after the transaction was sent
- network setting silently ignored
Around it
Before: agent-wallets.fund-and-cap. After: accounting.record-expense.
Where this comes from
Weight 16 of 100 in Agent wallets & spending controls: 4 of 20 accounts (acc-04, acc-09, acc-10, acc-11); double payment after an ambiguous failure is reported in both HN and GitHub
The same as data: /api/v1/use-cases/agent-wallets.send-and-confirm.json, or the MCP tool get_use_case with id agent-wallets.send-and-confirm. 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.