# Send a payment and confirm it landed without sending twice

> Send a payment and confirm it landed without sending twice: 2 companies fully do it, 6 with a limit, 13 carry the tag. Every listing in Agent wallets & spending controls with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-wallets.send-and-confirm/
- Markdown: https://www.anchorterminal.com/niches/agent-wallets.send-and-confirm/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-wallets.send-and-confirm/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-wallets.send-and-confirm/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 6 | 13 | 16 | 4 |

## 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

The docs show it meets the test above, and nothing we read says otherwise.

- **FluxA AI Wallet (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.
- **Turnkey Agentic Wallets (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.

## Does the job, with a limit

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.

- **Circle Wallets (Agent Wallets, Programmable Wallets) (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.
- **Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) (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).
- **Kite Agent Passport (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.
- **Openfort (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.
- **Privy Wallets (server wallets, agent wallets, policy engine) (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.
- **Sponge Wallet (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.

- not this job: Agentcard (Agentcard Corporation): No onchain transfers.
- not this job: Agent Vault by Self (SocialConnect Labs, Inc., doing business as Self Labs): No onchain transfers.
- not this job: Yield.xyz MCP server (Omni Ltd. (Yield.xyz)): No transfers; submit_hash only records a hash the caller's signer produced.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-wallets.send-and-confirm.json, or the MCP tool get_use_case with id agent-wallets.send-and-confirm. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
