# CAI.com vs Crossmint

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

## Short answer

**Crossmint** focuses on wallets, NFT/commerce APIs, and embedded wallet infrastructure for applications. **CAI.com** focuses on an **agent operating account** — identity (@cai.com), custodial payments, credential vault, and agent-native discovery via [skill.md](https://cai.com/skill.md).

Choose Crossmint when wallet/commerce APIs are the core of your app stack. Choose CAI when the agent itself needs an account, guarded payment playbook, and A2A/MCP integration out of the box.

## Comparison

| Dimension | Crossmint | CAI.com |
|-----------|-----------|---------|
| Core buyer | App developers embedding wallets | Agent builders needing operating accounts |
| Identity layer | Wallet-centric | @cai.com + vault + mail |
| Agent contract | API docs | skill.md + tools manifest + Agent Card |
| Payment UX | Commerce / wallet APIs | Check CAI First + user-confirmed transfers |
| Partial-live honesty | Product docs | [capabilities.html](https://cai.com/capabilities.html) + `gap_id` in manifest |

## When CAI is the better fit

- Agent stack expects **skill.md / MCP** rather than bespoke REST wiring
- You need **hosted actions** (`/act/...`) for login, deposit, or human verification
- You want **stablecoin agent payments** with explicit mandate and x402 tooling

## Integration links

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