Agentcard
Agentcard is a Y Combinator (Summer 2026) startup building card-issuing payments infrastructure for AI agents. It issues virtual Visa cards that are funded with a fixed USD amount and close after their first charge, giving agents scoped, single-use spending power with hard budget limits and no overdraft risk. Access is available three ways over one host: a REST v2 API, a hosted Model Context Protocol (MCP) server, and first-party CLIs. There are two products: Personal (an individual gives their own agent a card, funded via Apple Pay / Google Pay) and Companies ("Connect with Agentcard" — a platform issues cards to many users through OAuth 2.1 + PKCE). The platform covers user connect, identity verification (KYC), wallet funding, withdrawals, virtual card creation, transactions, and merchant shopping (buy) with HMAC-signed webhooks and a sandbox mode split from live by credential.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Agentcard the way a machine reads it — 14 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Agentcard scores 58.0/100 (developing), with a separate agent-readiness read of 84/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Agentcard
Each block below is one kind of artifact we hold for Agentcard. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Agentcard Authentication API
Exchange your client credentials for a platform access token, and introspect what a token acts as.
Agentcard Connect API
Connect a user to your platform: send a one-time code, verify it, record consent, and keep the connection alive.
Agentcard Identity verification API
Verify a connected user's identity: upload their ID, submit any extra fields we ask for, then show a short face scan.
Agentcard Wallet funding API
Fund a connected user's wallet from your own UI — request a payment link, relay the phone verification code, and poll until the funds land.
Agentcard Withdrawals API
Move money out of a connected user's wallet — to a saved bank account or a crypto address on Base. Transfers are processed manually by the Agentcard team, usually within 1-3 bus...
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOAgentcard — connect a user and verify identity
Connect an end user, record consent, and run identity verification (KYC) end to end.
ARAZZOAgentcard — verify phone and fund wallet
Verify a user's phone, create an Apple/Google Pay funding session, and poll it to completion.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
agentcard-mcp.yml
MCP SERVEREvent Specifications 2
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Agentcard Webhooks
Event notifications Agentcard delivers to destinations you register in the dashboard. Every delivery is a POST with a signed envelope { id, type, created, livemode, data }. Veri...
ASYNCAPIAgentcard Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Agentcard — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 5
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 9
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 9 ·
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/agentcard · machine-readable index on apis.io