Issue an agent card
Issue a virtual card for the authenticated agent, as POST /cards with agentId does for the platform. The card belongs to the agent’s customer, who must have KYC status APPROVED and have accepted the cardholder agreement where the platform requires one. Its spend is the customer’s own and does not count against the agent’s policy, and Grid’s default agent merchant-category blocks apply. Requires the ISSUE_CARDS permission; reading the card afterwards needs MANAGE_CARDS. While any of the agent’s cards is not CLOSED, including one the platform issued for it, the request is rejected with AGENT_CARD_EXISTS.
Card issuance is fee-bearing and cannot be reversed, so an Idempotency-Key header is required. Keys are scoped to the agent: a retry by the same agent with the same key returns the card the first request created, even though that card is now live, and another agent’s key never matches.
New cards start in status: "PROCESSING" and follow the same status transitions and card.status_change webhooks as cards issued with POST /cards.
Authorizations
Bearer token authentication for agent-scoped endpoints. The token is the accessToken returned when redeeming a device code via POST /agents/device-codes/redeem. Agent credentials are user-scoped: all requests are automatically bound to the agent's associated customer and subject to the agent's policy.
Headers
A unique identifier for the request, up to 255 characters, scoped to the agent. A retry carrying the same key returns the card created by the first request; reusing a key for a different card request is rejected with 409.
255"550e8400-e29b-41d4-a716-446655440000"
Body
Internal account id that funds the card. The account must belong to the agent's customer and be denominated in a card-eligible currency; otherwise the request is rejected with INVALID_INPUT.
"InternalAccount:019542f5-b3e7-1d02-0000-000000000002"
Response
Card created. It starts in PROCESSING while the issuer provisions it.
A card that belongs to the authenticated agent: the card itself and how the agent may use it.
The agent the card belongs to.
"Agent:019542f5-b3e7-1d02-0000-000000000042"
How an agent card is used and funded.
STANDARD Every merchant category code the card declines: blockedMccs plus the categories Grid blocks for agent cards, unless the platform lifted those defaults (defaultMccBlocksLifted).
^[0-9]{4}$