{
  "listings": [
    {
      "slug": "circle-wallets",
      "name": "Circle Wallets (Agent Wallets, Programmable Wallets)",
      "company": "Circle Technology Services, LLC",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://developers.circle.com/agent-stack/agent-wallets/wallet-operations/custom-policies.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/circle-wallets"
    },
    {
      "slug": "coinbase-cdp-agentkit",
      "name": "Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP)",
      "company": "Coinbase, Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://docs.cdp.coinbase.com/server-wallets/v2/using-the-wallet-api/policies/overview.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/coinbase-cdp-agentkit"
    },
    {
      "slug": "openfort",
      "name": "Openfort",
      "company": "Alamas Labs Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://www.openfort.io/docs/configuration/policies.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/openfort"
    },
    {
      "slug": "privy",
      "name": "Privy Wallets (server wallets, agent wallets, policy engine)",
      "company": "Horkos, LLC",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://docs.privy.io/controls/policies/overview.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/privy"
    },
    {
      "slug": "turnkey-agentic-wallets",
      "name": "Turnkey Agentic Wallets",
      "company": "Turnkey Global, Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://docs.turnkey.com/solutions/company-wallets/agentic-wallets.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/turnkey-agentic-wallets"
    },
    {
      "slug": "sponge-wallet",
      "name": "Sponge Wallet",
      "company": "Sponge Inc.",
      "grade": "F",
      "fit": "unchecked",
      "why": "Whether every send type is checked by the limits and which keys bypass them is documented only on the refused docs host.",
      "confidence": "low",
      "url": "https://www.anchorterminal.com/tools/sponge-wallet"
    },
    {
      "slug": "agentcard",
      "name": "Agentcard",
      "company": "Agentcard Corporation",
      "grade": "C",
      "fit": "no",
      "why": "Cards, not wallet signing; no transaction, typed-data or hash policy.",
      "source": "https://docs.agentcard.com/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/agentcard"
    },
    {
      "slug": "fluxa-ai-wallet",
      "name": "FluxA AI Wallet",
      "company": "FluxA Technology Pte. Ltd.",
      "grade": "E",
      "fit": "no",
      "why": "Personal mandates and per-payout approval only; no company wallet policy over transaction types or a named approver above a threshold.",
      "source": "https://docs.fluxapay.xyz/cli/payments.html",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/fluxa-ai-wallet"
    },
    {
      "slug": "kite-agent-passport",
      "name": "Kite Agent Passport",
      "company": "Datalego Inc.",
      "grade": "D",
      "fit": "no",
      "why": "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": "https://docs.gokite.ai/kite-agent-passport/cli-reference",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/kite-agent-passport"
    },
    {
      "slug": "self-agent-vault",
      "name": "Agent Vault by Self",
      "company": "SocialConnect Labs, Inc., doing business as Self Labs",
      "grade": "D",
      "fit": "no",
      "why": "No company wallet or signing policy over transaction types; controls are card-fill rules.",
      "source": "https://docs.agentvault.io/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/self-agent-vault"
    },
    {
      "slug": "yield-xyz-mcp",
      "name": "Yield.xyz MCP server",
      "company": "Omni Ltd. (Yield.xyz)",
      "grade": "BB",
      "fit": "no",
      "why": "No signing or policy engine; actions tools never sign or broadcast.",
      "source": "https://docs.yield.xyz/documentation/ai-agents/mcp-server.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/yield-xyz-mcp"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "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"
  },
  "useCase": {
    "accounts": 3,
    "after": [
      "agent-wallets.revoke-and-audit",
      "accounting.journal-entry"
    ],
    "area": "payments",
    "asks": [
      "let the agent pay suppliers only from the treasury wallet",
      "require my approval above 500",
      "only allow transfers to these addresses"
    ],
    "before": [
      "secrets.issue-agent-key"
    ],
    "blockers": [
      "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"
    ],
    "capabilities": [
      "wallet.custody",
      "wallet.spend-limits",
      "wallet.allowlist",
      "wallet.approval"
    ],
    "category": "agent-wallets",
    "categoryName": "Agent wallets \u0026 spending controls",
    "checked": "2026-11-15",
    "companies": {
      "fit": 0,
      "fitWithLimit": 5,
      "tagged": 11
    },
    "competition": "none",
    "fits": null,
    "fitsWithLimit": [
      "circle-wallets",
      "coinbase-cdp-agentkit",
      "openfort",
      "privy",
      "turnkey-agentic-wallets"
    ],
    "id": "agent-wallets.policy-signing",
    "listings": {
      "caveat": 5,
      "no": 5,
      "notRead": 0,
      "tagged": 12,
      "unchecked": 1,
      "yes": 0
    },
    "name": "Sign from a company wallet under allow-lists and approval rules",
    "status": "draft",
    "success": "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.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/agent-wallets.policy-signing.json",
    "weight": 14,
    "weightBasis": "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"
  }
}
