CORAL
Identity, custody, and spend controls for agent commerce

Payments and Identity for AI Agents

Create agent wallets, assign handles, enforce spending rules, and move money through simple APIs.

Start BuildingView Docs

How It Works

A simple payment flow for humans and autonomous software.

Claim a handle

Users and agents get readable identities like @alex or @trading_bot instead of wallet addresses.

Create a wallet

Coral provisions embedded Base and Solana wallets with encrypted keys and a path to MPC custody.

Move money

Resolve handles, enforce policy, create claim links, and record every transfer.

Core Platform

Infrastructure for the next payment actor.

Coral gives agents the primitives products already expect for humans: identity, permissioned wallets, history, and a payment path that feels native.

Abstract Coral Network interface connecting handles, wallets, claim links, and API controls
15m
access
30d
refresh
USDT default

Agent wallets

Programmable wallets with human-readable owners.

Create wallets for AI agents, assign handles, set active states, and keep wallet custody isolated from user-facing flows.

Per-agent handlesEncrypted private keysActive and inactive states

Handle payments

Send to @handles, not hexadecimal strings.

Coral resolves each handle to a wallet, routes payments, and preserves the transaction context that product teams need.

Unique namespaceInstant resolutionTransaction history

Developer APIs

A clean API surface for agent-native payments.

Issue API keys, list agents, send funds, inspect transactions, and integrate the payment layer into applications.

Bearer API keysAgent send endpointHandle lookup

Claim links

Pay people before they have an account.

When a handle does not exist, Coral creates a secure claim link so the recipient can sign up, claim the handle, and receive funds.

Missing-handle flowExpiring secretsRecipient onboarding

Developer APIs

Build payments into products without teaching agents wallet plumbing.

API keys are hash-stored, agent sends are policy-checked, and handle resolution gives developers a stable interface over wallet complexity.

coral api
POST /api/v1/agents
POST /api/v1/agents/:id/send
GET /api/v1/handles/:handle
GET /api/v1/transactions

Security is part of the product surface.

Argon2 passwords
HTTP-only refresh cookies
Encrypted wallet keys
Hashed API keys
Server-side authorization
Audit logging hooks

FAQ

Questions before the first transfer.

Is Coral a wallet, payment network, or identity layer?

The MVP combines all three: embedded wallets, unique handles, policy controls, and payment APIs for humans and agents.

What happens when a recipient does not exist?

Coral creates a payment claim with a secret-backed URL. The recipient signs up, claims a handle, and receives the pending funds.

Can developers control agent spend?

Yes. Each agent can enforce daily and per-transaction limits before Coral creates a transfer.