{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/agent-wallets.policy-signing/",
    "json": "https://www.anchorterminal.com/niches/agent-wallets.policy-signing/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/agent-wallets.policy-signing/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/agent-wallets.policy-signing/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 5 | 11 | 14 | 3 |\n\n## What counts as done\n\nThe 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.\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **Circle Wallets (Agent Wallets, Programmable Wallets) (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.\n- **Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) (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.\n- **Openfort (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.\n- **Privy Wallets (server wallets, agent wallets, policy engine) (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.\n- **Turnkey Agentic Wallets (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).\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Sponge Wallet (Sponge Inc.)**: Whether every send type is checked by the limits and which keys bypass them is documented only on the refused docs host.\n\n- not this job: Agentcard (Agentcard Corporation): Cards, not wallet signing; no transaction, typed-data or hash policy.\n- not this job: FluxA AI Wallet (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.\n- not this job: Kite Agent Passport (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.\n- not this job: Agent Vault by Self (SocialConnect Labs, Inc., doing business as Self Labs): No company wallet or signing policy over transaction types; controls are card-fill rules.\n- not this job: Yield.xyz MCP server (Omni Ltd. (Yield.xyz)): No signing or policy engine; actions tools never sign or broadcast.\n\n## What stops agents finishing\n\n- a send path the policy engine does not evaluate\n- root or full API keys bypass the policy\n- confirm-before-signing exists only as a prompt instruction\n\n## Around it\n\nBefore: secrets.issue-agent-key. After: agent-wallets.revoke-and-audit, accounting.journal-entry.\n\n## Where this comes from\n\nWeight 14 of 100 in Agent wallets \u0026 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\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/agent-wallets.policy-signing.json, or the MCP tool get_use_case with id agent-wallets.policy-signing. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Sign from a company wallet under allow-lists and approval rules",
        "url": ""
      }
    ],
    "description": "Sign from a company wallet under allow-lists and approval rules: 0 companies fully do it, 5 with a limit, 11 carry the tag. Every listing in Agent wallets \u0026 spending controls with the reason and a source.",
    "facts": null,
    "h1": "Sign from a company wallet under allow-lists and approval rules",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/agent-wallets.policy-signing/",
    "published": "",
    "section": "agents",
    "title": "Sign from a company wallet under allow-lists and approval rules |…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/agent-wallets.policy-signing/"
  },
  "tokens": {
    "markdown": 1300,
    "slim": 280
  },
  "version": 1
}
