# Agentcard > Agentcard gives AI agents a way to pay at card checkouts. Its Vault stores a user's own cards for approved purchases, and Issuing creates single-use or multi-use virtual Visa cards. Access is by REST API, MCP server and CLI. - Canonical: https://www.anchorterminal.com/tools/agentcard - Markdown: https://www.anchorterminal.com/tools/agentcard.md (~9,500 tokens) - Slim: https://www.anchorterminal.com/tools/agentcard.min.md (~2,180 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/agentcard.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade C · 56.5/100 · rank #632 of 950 · #6 in Agent wallets & spending controls · not agent-ready · confidence medium** ## Assessment Purchases need the user's passkey approval by default, cards carry spending rules, and card creation takes an idempotency key. No status page, published rate limits beyond the token endpoint, or privacy policy of Agentcard's own was found, and the Trust Centre could not be read. Issuing costs $5,000 a month. ## Facts | Field | Value | | --- | --- | | Vendor | Agentcard Corporation (https://www.agentcard.sh) | | Kind | HTTP API | | Category | Agent wallets & spending controls (https://www.anchorterminal.com/categories/agent-wallets) | | Transport | HTTP | | Endpoint | `https://api.agentcard.sh` | | Auth | OAuth · Self-serve. A person signs in to the dashboard or the CLI with an emailed code and creates an OAuth client. `POST /api/v2/oauth/token` exchanges `client_id` and `client_secret` for a platform token that lasts one hour, with the single scope `api`. A user connects by a one-time code, which returns a connection token limited to that user's cards and purchases, refreshed with the platform token. Sandbox and production use separate clients on one host. | | Pricing | Freemium ($0.15 / call) · Vault is free up to 5,000 users, with Enterprise by quote. Issuing is $5,000 a month with $0 per card. The Purchase Agent is listed at $0.15 a request and free in beta. A sandbox with test cards needs no contract or card. Prices for the personal plans named in the MCP tools (free, basic, pro) were not found (https://www.agentcard.sh/pricing, checked 2026-10-09). | | x402 | No · The home page FAQ asks whether Agentcard supports x402, AP2 or other agent payment protocols and answers Not yet. No x402, MPP or L402 in the docs or the OpenAPI file (https://www.agentcard.sh/, checked 2026-10-09). | | Licence | Proprietary service under Agentcard's terms of use. The `agent-cards` CLI on npm declares no licence, `@agent-cards/checkout` is marked as having none, and the repository they name is private | | Packages | npm: `agent-cards`; npm: `@agent-cards/checkout` | | Docs | https://docs.agentcard.sh | | llms.txt | https://docs.agentcard.sh/llms.txt | | Last release | 2026-10-09 | | npm downloads / week | 33,018 | | Custody | Vault cards are encrypted on the user's device with a passkey before storage, and the site says Agentcard never sees the full number. Issued cards draw on a balance held as USDC on Base as collateral, per the terms and the Issuing page | | Spending limits | Each issued card holds a set amount in cents (minimum 100). Presets add caps in total and per rolling 24 hours, 7 days and 30 days, plus merchant, category, country, currency, day and hour rules, in `strict` or `watch` mode | | Approvals | Vault purchases wait for the user's passkey or master password. Production `POST /api/v2/cards` returns `approval_pending` with an `approval_url`. Users can opt in to auto-approval under an amount and budget they set, and can require approval for each reveal of card details | | Revocation | `pause_card`, `close_card`, `revoke_connection` and `agent-cards companies credentials revoke`. Connection tokens last one hour and each refresh invalidates the old pair | | Cards | Virtual Visa cards issued by Third National (Rain), single-use or multi-use with an optional expiry up to 365 days. The Vault stores Visa, Mastercard, American Express and Discover cards. No physical cards per the FAQ | | Funding | Apple Pay, Google Pay or card through MoonPay and Crossmint, or USDC on Base, held as USDC. A company wallet can fund users' cards. No ACH or wire per the FAQ. Wallet funding is US only per the terms | | Identity checks | Issuing needs KYC through Sumsub (document and face scan). The Vault needs none | | API | REST at https://api.agentcard.sh under `/api/v2`, plus `/buy`. OpenAPI 3.1.0 file, version 2.0.0, with 20 paths and 21 operations. Vault, preset and webhook endpoint routes are documented on Markdown pages only | | MCP | Streamable HTTP at https://mcp.agentcard.sh/mcp. The docs hold pages for 25 organisation tools and 92 user tools. The overview lists 39 user tools, and others are hidden unless `x-expert-tools: 1` is sent. A shopping-only connection gets only shopping tools | | CLI | `agent-cards` 0.8.2 on npm (28 September 2026), Node 22 or later, 116 documented commands. `agent-cards api` lists, describes and calls every account tool with JSON output | | Credentials | OAuth 2.0 client credentials. `client_id` and `client_secret` (`acs_`) per sandbox or production client, platform tokens for one hour with scope `api`, user connection tokens (`act_`) with rotating refresh tokens (`rct_`), and public PKCE clients | | Rate limits | 30 requests per 5 minutes per IP on `POST /api/v2/oauth/token`. The MCP `create_card` tool can return `rate_limited` with advice to wait about a minute. No other figure found | | Errors | `{"error":{"code","message","docs"}}` with a stable `code`. MCP tools return a `status` discriminator that names the next step, such as `kyc_required` or `approval_pending` | | Webhooks | Signed with HMAC-SHA256 in `AgentCard-Signature`, delivered at least once, retried up to five times over about 96 minutes, with a delivery log by API and dashboard | | SDKs | `@agent-cards/checkout` 0.23.6 on npm (9 October 2026) for Playwright and CDP browsers. No Python SDK found | | Card fees | No annual fee, 0 per cent APR, 1 per cent on international transactions and a late fee of 2 per cent of the outstanding balance, per the card terms of 10 July 2026 | | Status | No status page found on the site or in the docs. An SLA is listed for the Enterprise plans only | | Capabilities | payments.card, wallet.spend-limits, wallet.custody | | Tags | hosted, freemium, closed-source, openapi, llms-txt, mcp, cli, oauth, typescript, sandbox, webhooks, virtual-cards, cards, approvals, usdc | | JSON | https://www.anchorterminal.com/api/v1/tools/agentcard.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 29 | 5.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 80 | 13.0 | | Agent ergonomics | 13% | 16.2 | 63 | 10.2 | | Security & auth | 14% | 17.5 | 68 | 11.9 | | Payments & pricing | 10% | 12.5 | 42 | 5.2 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 74 | 6.5 | | Transparency & trust (editorial 36, provenance 51) | 7% | 8.8 | 44 | 3.9 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **56.5 → C** | ### Why each score - Reliability 29: Graded as a hosted service on the REST API at api.agentcard.sh and the MCP server at mcp.agentcard.sh. No status page was found. The site footer and the docs link none (0). With no readable incident history the record takes the default (5). The changelog of 22 September 2026 records a fixed startup failure in which a deploy could make every API request return an error, with no duration. The only rate limit with numbers is 30 requests per 5 minutes per IP on the token endpoint, and the MCP `create_card` tool can answer `rate_limited` with advice to wait about a minute (5 of 15). `POST /api/v2/cards` requires an `Idempotency-Key`, `buy_checkout` and the organisation `create_card` tool take an `idempotency_key`, webhooks are delivered at least once with advice to deduplicate on `id`, and the docs say never to retry a payment automatically. No 429 response or `Retry-After` header is documented (10 of 15). The pricing page lists an SLA with uptime and response-time guarantees for the Enterprise plans, and no SLA text is published (3 of 10). Vault and Issuing carry no beta label. The Purchase Agent is free in beta, `create_card` can return `beta_capacity_reached`, and the CLI is at 0.8.2 (6 of 10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 80: A public OpenAPI 3.1.0 file at docs.agentcard.sh/openapi.json, version 2.0.0, with 20 paths and 21 operations for tokens, connections, identity checks, `/buy` and cards. The Vault, preset, webhook endpoint and Blooio routes in the API reference are Markdown pages with no entry in the file. Each MCP tool has a page with typed inputs and returns (17 of 25). We read the description file and the Markdown pages, not the rendered reference. llms.txt indexes 379 pages, each with a Markdown twin (10). Tool and endpoint descriptions say what a call does, when to use it and when not to, for example that `get_card_details` is for the payment form only and `get_card_balance` is preferred otherwise (17 of 20). The OpenAPI file has 36 enums and 31 required lists, and amounts are integers in cents. `/buy` takes free text in `ask`, and `preset` accepts a name, a list, inline JSON or an object (11 of 15). Every operation documents error responses with named codes, the file holds 37 examples, and MCP pages show captured error results (13 of 15). The API is versioned in the path as `/api/v2`, the older `/api/v1/oauth/token` path still answers, and a public changelog is dated almost daily to 28 September 2026. The changelog mixes product and API changes and the OpenAPI version has no dated history (12 of 15). - Agent ergonomics 63: The docs hold pages for 92 user tools and 25 organisation tools on the MCP server, which is the more-than-30 band (5). The overview lists 39 user tools, others stay out of the default `tools/list` unless the client sends `x-expert-tools: 1`, the credential picks the toolset, a shopping-only connection gets only shopping tools, and `buy` runs a whole purchase as one tool (8 back, 13 of 25). We did not connect to the live server, so counts are from the docs. `list_transactions` takes `limit`, `offset`, `status` and `card_id`. No cursor or page size was found on the REST list routes (8 of 20). Errors use one envelope with a stable `code`, a message safe to log and a docs link, each endpoint page lists its codes, and MCP results carry a `status` that names the next tool to run (18 of 20). `POST /api/v2/cards` requires an `Idempotency-Key`, `buy_checkout` reuses one reservation per `idempotency_key`, and tool pages state each tool's behaviour as read-only, idempotent or destructive. Whether the live tool definitions carry the matching annotations was not checked (16 of 20). `create_card` needs only `amount_cents`. `@agent-cards/checkout` is a TypeScript SDK for Playwright and CDP browsers and the CLI is on npm. No SDK in a second language was found (8 of 15). - Security & auth 68: OAuth 2.0 client credentials. Client secrets are shown once, clients are separate for sandbox and production and can be revoked, platform tokens last one hour, and user connection tokens last one hour with refresh tokens that rotate on each use. Platform tokens carry the single scope `api`, and the MCP guide sends the client secret itself as the bearer for organisation tools. No secret travels in a URL (23 of 30). Vault purchases wait for the user's passkey or master password by default, production card creation returns `approval_pending`, users can require approval for each reveal of card details, and presets cap spend and restrict merchants, categories, places, currencies and hours. A connected app gets `read_only` when it tries to change presets, and approval tools answer `personal_surface_only` to a connected session. An app's auto-approval permission on a saved card has no spending limit or end date per the docs (18 of 20). The Purchase API returns merchant catalogue text to the agent. Money moves only when the agent echoes a cart `hash`, `buy_checkout` re-checks `expected_total_cents` and the address, and preset rules ignore the `merchant` text an agent sends. No guidance that names untrusted content or prompt injection was found (9 of 15). Webhooks cover cards, transactions, approvals and orders, deliveries are logged, each read of card credentials notifies the member, and transactions are listed by API and tool (11 of 15). The site links a Trust Centre on app.vanta.com, which robots.txt closed to us, and the Enterprise plans list a SOC 2 report and a pen-test summary. security.txt returned 404, and no disclosure policy or bug bounty was found. The changelog reports security fixes, among them a webhook address check on 27 September 2026 (7 of 20). - Payments & pricing 42: Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Agentcard pays by card. The home page FAQ answers Not yet on x402, AP2 and other agent payment protocols, and none appears in the docs (0 of 40). The pricing page is public. Vault is free up to 5,000 users, Issuing is $5,000 a month with $0 per card, the Purchase Agent is $0.15 a request and free in beta, and the card terms give 1 per cent on international transactions. Enterprise prices and the personal plan prices were not found (17 of 20). The Vault Free plan and a sandbox with test cards need no payment card or contract (20). A person signs in with an emailed code, in a browser or with `agent-cards login --email` and `--code`, and the CLI then mints sandbox credentials. An agent cannot get access without that person's inbox, and Issuing adds an identity check (5 of 20). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 74: `@agent-cards/checkout` 0.23.6 was published on 9 October 2026, `agent-cards` 0.8.2 on 28 September 2026, and the newest changelog entry is dated 28 September 2026 (30). `agent-cards` had 44 versions between 11 July and 28 September 2026, and the changelog has 147 dated entries from 27 February to 28 September 2026 (20). The service is closed and the repository named in the packages is private. Support is an email address, a support chat reachable through MCP tools and the CLI, and an `ask_agentcard_engineer` tool. None was tested (10 of 15). The CLI and the TypeScript checkout SDK are current. Presence in the official MCP registry was not checked (10 of 15). The CLI has 19 runtime dependencies, needs Node 22 or later and declares no licence. CI is not visible (4 of 10). - Transparency & trust 44: A closed service. The repository named in the npm packages is private, `agent-cards` declares no licence and `@agent-cards/checkout` is marked as having none. The terms of use, updated 10 July 2026, name the legal entity and its addresses, cover the API, MCP server and CLI, and state what a card is and who issues it (13 of 30). No privacy policy of Agentcard's own was found. The terms refer to our Privacy Policy and link Rain's, and Rain's policy says partners may be responsible for their own notices. The site says Vault cards are encrypted on the user's device, and the changelog of 24 September 2026 says stored card numbers from retired issuing paths were purged. No retention period or public DPA was found (8 of 30). The older token path is kept with a note, and the CLI README says API keys are retired and the admin package forwards to the new one. No deprecation policy or dated notice was found (5 of 20). The terms name MoonPay, Crossmint, Coinbase, Third National, Sumsub, Visa and Stripe, with no data locations. The CLI README discloses telemetry and two settings that turn it off (10 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (29 items): https://www.anchorterminal.com/fixes/agentcard.md (JSON https://www.anchorterminal.com/fixes/agentcard.json) ### What we couldn't check - unchecked: the Trust Centre at app.vanta.com, whose robots.txt disallows every path. Certifications, policies and any subprocessor list there were not read and score as absent - unchecked: the tools the live MCP server lists and whether they carry read-only and destructive annotations. We did not connect. Counts and behaviour labels are from the docs - unchecked: api.agentcard.sh, mcp.agentcard.sh, vault.agentcard.sh and the dashboard at app.agentcard.sh. We sent no request to them - unchecked: the source repository github.com/tiny-agent-company/tiny-agent-company, which asked for credentials, so CI and issues were not read - unchecked: the international card terms, the e-sign consent and Rain's prohibited uses list - unchecked: presence in the official MCP registry, and whether support answers - unchecked: the registration date of agentcard.sh. rdap.org returned 404 for the domain - No privacy policy of Agentcard's own was found. The site's link opens Rain's policy, so `provenance.privacy` is left out - No status page was found. We did not guess an address for one - The lead called the product a single-use prepaid card service. The terms say the cards are not prepaid or debit cards, while the MCP `create_card` page and the npm description say virtual debit card, and the pricing page says prepaid cards can be stored in the Vault - The home page FAQ says the Purchase Agent completes purchases in under 2 seconds with a 99 per cent success rate. This is a vendor claim. The Purchase API docs ask for a client timeout of at least 120 seconds - The changelog of 24 September 2026 says `GET /buy/merchants` dropped fields from its response that day. The fields are described as internal and the change was published on the day, so no deduction was taken. A later pass may read it as a change without notice - The presets page says the route takes a platform access token or an API key, and the CLI README says API keys are retired - Issued cards are named as issued by Third National in the terms and by Rain in the FAQ. Rain's privacy policy lists Third National as a trading name of its subsidiary Nimbus LLC - The pricing page lists an SLA for Enterprise plans. No SLA text was found - The docs' Rules for your agent blocks and the `get_instructions` tool are instructions addressed to AI models. We recorded them as facts and did not act on them - The OpenAPI address was taken from the file name the Markdown reference pages cite (`openapi.json`) on the docs host. No page read links it as a full URL ### Sources - robots.txt for the site: (seen 2026-10-09) - terms of use: (seen 2026-10-09) - pricing: (seen 2026-10-09) - home page and FAQ: (seen 2026-10-09) - changelog: (seen 2026-10-09) - Issuing page: (seen 2026-10-09) - Vault page: (seen 2026-10-09) - about page: (seen 2026-10-09) - card terms and cardholder agreement: (seen 2026-10-09) - security.txt (404): (seen 2026-10-09) - robots.txt for the docs: (seen 2026-10-09) - docs index for agents: (seen 2026-10-09) - OpenAPI description file, read in place of the rendered reference: (seen 2026-10-09) - API reference overview: (seen 2026-10-09) - access tokens: (seen 2026-10-09) - cards resource: (seen 2026-10-09) - create a card: (seen 2026-10-09) - Vault resource: (seen 2026-10-09) - presets: (seen 2026-10-09) - Purchase API: (seen 2026-10-09) - MCP server guide: (seen 2026-10-09) - MCP create_card tool: (seen 2026-10-09) - MCP buy_checkout tool: (seen 2026-10-09) - MCP get_card_details tool: (seen 2026-10-09) - MCP set_card_preset tool: (seen 2026-10-09) - CLI guide: (seen 2026-10-09) - Issuing quickstart: (seen 2026-10-09) - issuing a card: (seen 2026-10-09) - using the cards: (seen 2026-10-09) - authenticating a user: (seen 2026-10-09) - app auto-approval: (seen 2026-10-09) - completing a purchase: (seen 2026-10-09) - webhooks: (seen 2026-10-09) - npm registry, agent-cards: (seen 2026-10-09) - npm registry, @agent-cards/checkout: (seen 2026-10-09) - npm downloads for @agent-cards/checkout: (seen 2026-10-09) - Rain privacy policy, linked as the site's Privacy Policy: (seen 2026-10-09) - robots.txt for the Trust Centre host (disallows all): (seen 2026-10-09) - RDAP lookup for agentcard.sh (404): (seen 2026-10-09) ## Who's behind it (provenance 51/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Agentcard Corporation | 20/20 | | Domain age | agentcard.sh, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | api.agentcard.sh | 15/15 | | Terms of service | read, states 5 of the 7 things a reader expects, and has 1 clause that costs points | 6.3/10 | | Privacy policy | not found | 0/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The terms of use (updated 10 July 2026) name Agentcard Corporation, a Delaware corporation (File No. 10619012), registered office 131 Continental Dr, Suite 305, Newark, DE 19713, and cover the MCP server, CLI, dashboard and API. No privacy policy of Agentcard's own was found, so `privacy` is left out. The footer's Privacy Policy link and the link in the terms open Rain's privacy policy at legal.raincards.xyz, and www.agentcard.sh/privacy redirects to Rain's account opening privacy notice for Third National. Cards are issued by Third National, a Rain company, under a cardholder agreement at https://www.agentcard.sh/card-terms. The API answers at api.agentcard.sh, the MCP server at mcp.agentcard.sh and the Vault at vault.agentcard.sh per the docs. We sent no request to those hosts. www.agentcard.sh/.well-known/security.txt returned a 404 page. No status page was found. rdap.org returned 404 for agentcard.sh, so the registration date is unknown. The first `agent-cards` package was published on 23 February 2026. The npm packages name the private repository github.com/tiny-agent-company/tiny-agent-company. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.agentcard.sh/terms), read 2026-10-09, dated 2026-07-10, states 5 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "Use automated means exceeding reasonable use" - To know. Requires arbitration or waives class actions. "If unresolved within 30 days, either party may initiate binding arbitration in San Francisco, California." - Gives the date it was last updated. Last updated 2026-07-10. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). The service issues single-use virtual Visa cards designed for use by AI agents on behalf of a verified human account owner. "Agentcard provides single-use virtual Visa cards designed for use by AI agents on behalf of a verified human account owner." - Also in the text (2026-10-08). Amounts funded to the wallet are non-refundable except where the law requires a refund. "Funded amounts are non-refundable except as required by applicable law." **Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0. ## Live (updated 2026-10-10 02:06 UTC) - Right now: up, HTTP 404, 249 ms, checked 2026-10-10 02:06 UTC (get on `https://api.agentcard.sh`) - Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 199 ms · p95 505 ms - npm `@agent-cards/checkout` 0.23.6 - npm `agent-cards` 0.8.2 - Watching changelog - Watching pricing - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/agentcard.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Purchase Agent request (listed price, free in beta) | $0.15 | per call | https://www.agentcard.sh/pricing | | Issuing plan | $5000 | per month (plan) | $0 per card, 1 per cent revenue share to the customer | | Vault Free plan, up to 5,000 users | free | per month (plan) | Enterprise by quote | | Issued card international transaction | 1% | percentage fee | no annual fee, 0 per cent APR | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Vault purchases pause for the user's passkey or master password approval by default, and production card creation returns `approval_pending` with an approval link - Presets cap spend in total and per rolling day, week and month, and restrict merchants, categories, countries, currencies, days and hours, in `strict` or `watch` mode - `POST /api/v2/cards` requires an `Idempotency-Key`, and `buy_checkout` re-checks the confirmed total and address before paying - Errors share one envelope with a stable `code`, and each endpoint page lists the codes it can return - llms.txt indexes 379 Markdown pages, among them one page for each of 117 MCP tools and 116 CLI commands - Changelog entries are dated almost daily to 28 September 2026, and `@agent-cards/checkout` 0.23.6 was published on 9 October 2026 ## Weaknesses - No status page or incident history was found on the site or in the docs. An SLA is listed for Enterprise plans only, with no published text - The only rate limit with numbers is 30 requests per 5 minutes per IP on the token endpoint - The site's Privacy Policy link opens the policy of Rain, the card issuing partner. No privacy policy of Agentcard's own was found - The OpenAPI file covers 21 operations and leaves out the Vault, preset and webhook endpoint routes documented in the API reference - The home page FAQ answers Not yet on x402, AP2 and other agent payment protocols - An app's auto-approval permission on a saved card has no spending limit or end date, per the Vault docs - Platform access tokens carry one scope, `api`, and the MCP guide sends the client secret itself as the bearer ## Before you call it (notes for agents) 1. Mint a platform token with `POST /api/v2/oauth/token` and cache it for its one hour. The endpoint allows 30 requests per 5 minutes per IP 2. Send the same `Idempotency-Key` on every retry of `POST /api/v2/cards`, and the same `idempotency_key` on every retry of `buy_checkout` 3. Pass `source: "issued"` to the MCP `create_card` tool for a card number. Without it the tool may start Vault setup and return a link 4. Call `get_card_details` only at the payment form and never log the result. Each read notifies the member and may return `approval_required` 5. Treat `transaction.authorized` and `order.*` webhooks as the record of a payment, and deduplicate deliveries on the event `id` ## Connect Install: ```bash npm install -g agent-cards ``` First request: ```bash curl -X POST https://api.agentcard.sh/api/v2/oauth/token -d grant_type=client_credentials -d client_id=$AGENTCARD_CLIENT_ID -d client_secret=$AGENTCARD_CLIENT_SECRET ``` Claude Code: ```bash claude mcp add agentcard --transport http https://mcp.agentcard.sh/mcp --header "Authorization: Bearer YOUR_CLIENT_SECRET" ``` Through letme (picks today, calling later): https://letme.dev/agentcard. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Sponge Wallet | E | 43.2 | 884 | wallet.spend-limits, payments.card, wallet.custody | no | https://www.anchorterminal.com/tools/sponge-wallet.md | | Turnkey Agentic Wallets | BB | 76 | 39 | wallet.spend-limits, wallet.custody | no | https://www.anchorterminal.com/tools/turnkey-agentic-wallets.md | | Circle Wallets (Agent Wallets, Programmable Wallets) | BB | 73.9 | 80 | wallet.custody, wallet.spend-limits | no | https://www.anchorterminal.com/tools/circle-wallets.md | | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) | BB | 71.2 | 134 | wallet.custody, wallet.spend-limits | no | https://www.anchorterminal.com/tools/coinbase-cdp-agentkit.md | | Openfort | BB | 70.1 | 163 | wallet.spend-limits, wallet.custody | no | https://www.anchorterminal.com/tools/openfort.md | | Privy Wallets (server wallets, agent wallets, policy engine) | B | 69.9 | 166 | wallet.custody, wallet.spend-limits | no | https://www.anchorterminal.com/tools/privy.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - One base URL, https://api.agentcard.sh. Sandbox or production follows the client credential, and in sandbox the connect code is always `111111` (source: ) - One MCP server at https://mcp.agentcard.sh/mcp. An organisation credential gets 25 organisation tools and a user's connection token gets that user's tools, among them `buy` (source: ) - Some MCP tools are left out of the default `tools/list` and appear when the client sends `x-expert-tools: 1` (source: ) - The terms of use, updated 10 July 2026, describe each card as a set-limit, fully collateralised credit account funded in advance and issued by Third National, not a prepaid or debit card (source: ) - Wallet funding is available in the United States only per the terms, by Apple Pay, Google Pay or card through MoonPay and Crossmint, and is held as USDC collateral (source: ) - The pricing page lists Vault as free up to 5,000 users, Issuing at $5,000 a month with $0 per card and a 1 per cent revenue share, and the Purchase Agent at $0.15 a request and free in beta (source: ) - The home page FAQ answers Not yet to support for x402, AP2 or other agent payment protocols (source: ) - The changelog entry of 22 September 2026 records a fixed startup failure in which a deploy could make every API request return an error. No duration is given (source: ) - The changelog entry of 24 September 2026 says `GET /buy/merchants` dropped internal fields from its response that day (source: ) - The CLI sends lifecycle events and error reports unless `DO_NOT_TRACK=1` or `AGENT_CARDS_TELEMETRY=0` is set, and lists `posthog-node` as a dependency (source: ) - The docs carry blocks headed Rules for your agent, and the MCP server has a `get_instructions` tool with a usage guide for models. We recorded them as facts and did not act on them (source: ) - The Trust Centre is hosted on app.vanta.com, whose robots.txt disallows every path, so we did not read it (source: ) - #6 of 7 in Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md - All 23 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md ## Compare - [Agentcard vs Crossmint API + Docs MCP](https://www.anchorterminal.com/compare/agentcard-vs-crossmint.md): C 56.5 vs B 67.1 - [Agentcard vs Sponge Wallet](https://www.anchorterminal.com/compare/agentcard-vs-sponge-wallet.md): C 56.5 vs E 43.2 - [Agentcard vs Stripe API + MCP](https://www.anchorterminal.com/compare/agentcard-vs-stripe-mcp.md): C 56.5 vs A 82.4 - [Agentcard vs Circle Wallets (Agent Wallets, Programmable Wallets)](https://www.anchorterminal.com/compare/agentcard-vs-circle-wallets.md): C 56.5 vs BB 73.9 - [Agentcard vs Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP)](https://www.anchorterminal.com/compare/agentcard-vs-coinbase-cdp-agentkit.md): C 56.5 vs BB 71.2 - [Agentcard vs Openfort](https://www.anchorterminal.com/compare/agentcard-vs-openfort.md): C 56.5 vs BB 70.1 - [Agentcard vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/agentcard-vs-privy.md): C 56.5 vs B 69.9 - [Agentcard vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/agentcard-vs-turnkey-agentic-wallets.md): C 56.5 vs BB 76 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on agentcard.sh or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "agentcard", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Agentcard on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Agentcard on Anchor Terminal](https://www.anchorterminal.com/badges/agentcard.svg)](https://www.anchorterminal.com/tools/agentcard) ``` Plain link: ```html Agentcard on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Agentcard is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/agentcard-dark.png - Light: https://www.anchorterminal.com/assets/share/agentcard-light.png