Niches · Agent wallets & spending controls
Sign from a company wallet under allow-lists and approval rules
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 agent signs only operations the policy allows, every send type (transaction, typed data, hash) is checked by the same policy, operations above the threshold wait for a named approver, and the policy is enforced by the service, with each decision logged.
How agents ask for it: let the agent pay suppliers only from the treasury wallet
, require my approval above 500
, only allow transfers to these addresses
Does the job, with a limit 5
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 | Transfer limits and recipient and contract allow or block lists are enforced by Circle, but they skip token allowances (approve and transferFrom), the docs don't say sign message or typed-data is checked, and there is no approval-above-threshold step. source |
| Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) BB Coinbase, Inc. | The policy engine evaluates transaction, message, typed-data and hash signing per operation at project or account scope. Hash signing for end users takes no criteria, and no approval-above-threshold step with a named approver exists for server wallets. source |
| Openfort BB Alamas Labs Inc. | Rules run on each signing operation at account or project scope, fail-closed. Sends reach the engine only as signEvmHash and backend signTypedData is hashed locally so typed-data rules never match (acc-15); no approval-above-threshold step was found. source |
| Privy Wallets (server wallets, agent wallets, policy engine) BB Horkos, LLC | Rules cover each RPC method separately, including typed data, personal_sign, 7702 authorisations and key export, and key quorums set an authorisation threshold enforced in the TEE. The quorum threshold counts signers, not an amount above which a named person must approve, and no wait limit is stated. source |
| Turnkey Agentic Wallets BB Turnkey Global, Inc. | Policies cover transactions, EIP-712 typed data and other activity kinds, a consensus expression can require a named human above a value, and approvals expire after 24 hours. Root users bypass the engine entirely, and the skill's confirm-before-signing is a prompt with no verifiable record (acc-14, open). source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Sponge Wallet F Sponge Inc. | Whether every send type is checked by the limits and which keys bypass them is documented only on the refused docs host. |
Doesn't do this job 5
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Agentcard C Agentcard Corporation | Cards, not wallet signing; no transaction, typed-data or hash policy. source |
| FluxA AI Wallet E FluxA Technology Pte. Ltd. | Personal mandates and per-payout approval only; no company wallet policy over transaction types or a named approver above a threshold. source |
| Kite Agent Passport D Datalego Inc. | Sessions are a person's per-agent budgets; no company wallet policy over transaction types or a named approver above a threshold for agent payments. source |
| Agent Vault by Self D SocialConnect Labs, Inc., doing business as Self Labs | No company wallet or signing policy over transaction types; controls are card-fill rules. source |
| Yield.xyz MCP server BB Omni Ltd. (Yield.xyz) | No signing or policy engine; actions tools never sign or broadcast. source |
What stops agents finishing
- a send path the policy engine does not evaluate
- root or full API keys bypass the policy
- confirm-before-signing exists only as a prompt instruction
Around it
Before: secrets.issue-agent-key. After: agent-wallets.revoke-and-audit, accounting.journal-entry.
Where this comes from
Weight 14 of 100 in Agent wallets & spending controls: 3 of 20 accounts (acc-13, acc-14, acc-15); all builders, and the AgentKit policy-hook RFC (acc-13) has the longest thread read
The same as data: /api/v1/use-cases/agent-wallets.policy-signing.json, or the MCP tool get_use_case with id agent-wallets.policy-signing. 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.