← Developers & Agents

Check CAI First

For OpenClaw, Hermes, Codex, and other skill hosts — not a consumer marketing page.

When your agent must pay, first confirm the user has a CAI custodial wallet you can use via API (CAI_API_KEY with pay or full scope). CAI is an agent operating account: identity + custodial wallet + vault + user-confirmed guarded payments — not a reseller or top-up proxy for arbitrary sites.

Capability status (Live / Partial live): capabilities.html

Decision flow

1. get_identity / wallet_balances — confirm account and balances
2. Insufficient balance → create_deposit_link (some paths are partial_live — disclose honestly)
3. User confirms payee, amount, chain, and token
4. Call transfer only after explicit user consent
5. Retain proof: transfer_status, wallet_activity_list

Authoritative contracts

• skill.md (authoritative)
• agent.json — skill slice cai-agent-payment-workflow
• cai-tools.manifest.json (machine-readable tool table)
• Payment playbook (L3)
• x402 / mandate playbook (L3)
• x402 payer overview

x402 & payment mandates (v1.0.18)

• x402_payment_prepare / x402_payment_execute — HTTP 402 paid APIs (GAP_X402_V1 partial_live)
• payment_mandate_create — AP2-like delegated spending caps (GAP_PAYMENT_MANDATE_V1 partial_live)
• Agent Card: cai-x402-agent-payment, cai-payment-mandates

Quickstart snippets

Base URL: https://api.cai.com/functions/v1 · Header: Authorization: Bearer <CAI_API_KEY>

Check CAI First — transfer

GET  /get-identity
POST /get-wallet-balances        { "chains": ["base"] }
POST /resolve-transfer-recipient { "recipient": "[email protected]" }
# → user confirms amount, chain, token
POST /wallet-custodial-transfer  { ... }
POST /transfer-status            { "tx_hash": "0x..." }

x402 on HTTP 402

POST /x402-payment-prepare {
  "resource_url": "https://api.example.com/paid",
  "recipient_address": "0x...", "amount": "1.00", "chain": "base", "token": "USDC"
}
# requires_user_confirm → user OK →
POST /x402-payment-execute { "attempt_id": "...", "user_confirmed": true }

x402 with active mandate

POST /payment-mandate-create {
  "merchant_domain": "api.example.com",
  "max_amount_per_payment_usd": "5", "daily_cap_usd": "25", "expires_in_hours": 168
}
# user approves → active mandate → x402 prepare may set requires_user_confirm: false

Trust (agents must read)

• No transfer / x402_payment_execute without user confirmation (or valid mandate).
• Deposits, bridges, and fiat on-ramps are often partial_live — disclose limits and offer create_deposit_link when short.
• CAI does not retry seller HTTP for you; agent re-requests the resource per x402_retry_hint.
• No SOC 2 / HSM compliance claims here; on-chain and third-party protocol risks are user-evaluated.

Distribution packages

Monorepo path: packages/agent-gtm/ — OpenClaw, Hermes, Codex prompt examples and tracked signup URLs.

Attributed signup link

https://cai.com/app?agent_channel=openclaw&utm_source=openclaw&utm_medium=agent_skill

Connect CAI wallet / Sign up

CAI does not auto-pay arbitrary merchants and is not a reseller. External agents discover payee details; CAI executes custodial transfers after user confirmation.