Card attachment
The user attaches a card they already have. No wallet to fund — the agent
spends on the user’s own card, within the limits they set.
Card creation
Issue brand-new virtual cards funded from a wallet, with per-card limits
and single- or multi-use behavior.
Recommended flow
The fastest way to production is card attachment: the user connects, brings their own card, and your agent can spend — no wallet funding, no deposits to wait on. Implement it in three steps:1
User authentication
Connect the user to Agentcard from inside your own app. You build the
screens; we send the one-time code and hand back the user’s token.Follow the user authentication guide.
2
Card attachment
The user attaches their own Visa card for their agent to spend with — no
KYC, no wallet funding.Follow the card attachment guide.
3
MCP integration
Plug the Agentcard MCP server into your agent so it can see and use the
card.See MCP server.
API basics
Every guide calls the same API: one base URL (https://api.agentcard.sh), a
platform access token in the Authorization header, and a single error
envelope everywhere. The API reference covers all
of it, endpoint by endpoint, with a live playground.