Skip to main content
POST
Issue an agent card

Authorizations

Authorization
string
header
required

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

Idempotency-Key
string
required

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.

Maximum string length: 255
Example:

"550e8400-e29b-41d4-a716-446655440000"

Body

application/json
fundingSource
string
required

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.

Example:

"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.

card
object
required
agentId
string
required

The agent the card belongs to.

Example:

"Agent:019542f5-b3e7-1d02-0000-000000000042"

agentCardKind
enum<string>
required

How an agent card is used and funded.

Available options:
STANDARD
effectiveBlockedMccs
string[]
required

Every merchant category code the card declines: blockedMccs plus the categories Grid blocks for agent cards, unless the platform lifted those defaults (defaultMccBlocksLifted).

Pattern: ^[0-9]{4}$
Example: