How it works
Your agents connect to Reinx through the MCP server or REST API. Each agent gets:- A crypto wallet (non-custodial, USDC on Base/Polygon/Arbitrum/Optimism + Solana) for payments and agent-to-agent transactions
- Independent spending rules — per-payment limits, recipient controls, velocity caps, approval thresholds
- A virtual card (Visa & Mastercard) for merchant payments — launching with the card program
Key concepts
| Concept | Description |
|---|---|
| Crypto Wallets | Non-custodial wallets, USDC-native, gas sponsored |
| Virtual Cards | One card per agent, network-enforced limits (coming soon) |
| Spending Policies | Six layers of protection, deterministic enforcement |
| Approve/Deny | Human-in-the-loop for transactions above your threshold |
| Agent Health Score | Behavioral trust score (300–850), coming soon |
All financial controls are enforced by infrastructure, not by the agent’s code. Even a fully
compromised agent cannot bypass its spending rules.
Next steps
Quickstart
Give your agent a funded wallet with spending controls in minutes.
MCP Tools
Connect Claude, ChatGPT, or any MCP-capable agent to Reinx.
Authentication
Get an API key and make your first request.
Agents API
Create and manage agent accounts programmatically.