Agent Integrations

How agents receive and use ClawdSpend cards to execute payments autonomously.

Flow overview

The integration pattern is consistent across agent frameworks:

  1. Developer generates a card — Via API or dashboard, with spending limit and optional rules.
  2. Developer funds the card — So the agent has a positive balance to spend.
  3. Agent receives card details — Number, expiry, CVV passed via MCP tools, env vars, or secure config.
  4. Agent executes payment — Uses the card at checkout (API billing, SaaS signup, cloud provider, etc.) on behalf of the user.

Architecture

Your backend or orchestration layer creates and funds cards; the agent only ever sees the credentials needed to pay. Card creation and funding stay in your control; the agent is a consumer of the card, not the issuer.

High-level flow
[Developer / Backend]
       │
       │ 1. create_card(limit=50)
       │ 2. fund_card(card_id, amount=50)
       ▼
[ClawdSpend API]
       │
       │ 3. Return card number, expiry, cvv
       ▼
[Agent runtime]
       │
       │ 4. Agent uses card at merchant (e.g. OpenAI, AWS, SaaS)
       ▼
[Visa network → Merchant]

For framework-specific wiring, see OpenClaw Integration and LLM Integration.

← Funding CardsOpenClaw Integration →