# CAI.com vs Coinbase AgentKit

> Public comparison for agents and integrators. Verify live status at [capabilities.html](https://cai.com/capabilities.html).

## Short answer

**Coinbase AgentKit** is a developer SDK for giving agents on-chain wallet actions. **CAI.com** is an **agent operating account** — @cai.com identity, custodial wallet gateway, credential vault, user-confirmed payments, and machine-readable [skill.md](https://cai.com/skill.md) + [A2A Agent Card](https://cai.com/.well-known/agent.json).

Choose AgentKit when you already own the product UX and only need chain execution primitives. Choose CAI when the agent needs a persistent identity, email, vault, hosted human-in-the-loop actions, and an honest Live / Partial live capability matrix.

## Comparison

| Dimension | Coinbase AgentKit | CAI.com |
|-----------|-------------------|---------|
| Primary surface | SDK / framework integration | Operating account + REST / MCP / skill.md |
| Identity | App-defined | @cai.com email + account |
| Wallet model | Embedded / developer-managed patterns | Custodial gateway + user-confirmed `transfer` |
| Agent discovery | Docs + SDK | skill.md, manifest, agent.json, llms.txt |
| Payment rails | On-chain via SDK | Stablecoin transfer, x402, mandates (see `GAP_*` honesty) |
| Human confirmation | App responsibility | Product default: Check CAI First |

## When CAI is the better fit

- Agent must **sign in, receive mail, and pay** from one account
- You want **one machine-readable contract** for OpenClaw, Hermes, Codex, and REST
- You need **published gap_id** status instead of assuming all flows are production-complete

## Integration links

- [skill.md](https://cai.com/skill.md)
- [agent-payment-workflow.md](https://cai.com/skill-references/agent-payment-workflow.md)
- [agent-wallet-landscape.md](https://cai.com/skill-references/agent-wallet-landscape.md)