Payments infrastructure for AI agents.
ClearedAI is building the rails for autonomous agents to earn, hold, spend, and pay each other — inside our partner bank's regulated perimeter, never a standalone wallet. Humans set the limits. Every cent chains to a verified principal.
Control is the product.
Agent spending fails safe by construction — not by policy, not by dashboard.
Hard caps, set in stone
Cards are issued just-in-time with a fixed cap that cannot rise — the limit is enforced by the database, not by application code. Replenishment happens upstream at the funding pool, under the agent's mandate: the human-defined spending rules it operates within.
Invisible rotation
At 80% of cap a card retires itself and a replacement takes over mid-stream — merchants never notice, and every retirement links into an auditable chain. See how it works
A kill switch, not a support ticket
Revoke an agent and its next authorization declines in under a second — a machine-readable decline, zero side effects. Revoke a single service and everything else keeps working.
Mandate walls
Per-transaction caps, daily budgets, velocity limits, merchant-category allowlists — enforced inside the authorization decision itself. One budget spans card spend and agent-to-agent payments.
A ledger that can't lie
Double-entry, append-only, balances derived from history. Hand an auditor the complete, provable story of every cent — history that physically cannot be rewritten.
Verified humans behind every agent
Money exists here only at the end of a verified chain: human principal → agent → mandate → instrument. If the chain can't be traced, the money doesn't move.
The invisible swap.
Non-reloadable cards are safer. Rotating them used to break merchants. We made rotation invisible.
Spend against a hard cap
Every charge is modeled as a true two-phase hold: funds are earmarked instantly, settle on capture, and return on release or expiry.
At 80%, rotation arms
The moment spend crosses the threshold, a replacement card is issued with a fresh cap — automatically, mid-stream.
Tokens repoint. Merchants never notice.
The merchant-side token is repointed to the new card behind the scenes — no re-entry, no failed-payment emails, nothing for the merchant to do.
Retired cards join the chain
Every replacement links back to its predecessor, so the full history of an agent's spending power is auditable end to end.
One closed loop: earn, hold, spend, pay.
Agents don't just spend. They run real economic loops — on one ledger, inside one regulated perimeter.
Sales an agent makes settle straight into its pool — revenue lands on the same ledger that governs spend.
Pools are ledger balances inside the perimeter — computed from history, never a number anyone can edit.
Just-in-time cards with honest card semantics — the full two-phase lifecycle, detailed below.
Agents pay each other pool-to-pool under the sender's mandate — the same budget that governs card spend.
Honest card semantics.
Not a demo wrapper around a balance. The full two-phase lifecycle, modeled the way card networks actually work.
A hold earmarks pool funds atomically — checks, journal, and record commit together or not at all.
Settle up to the authorized amount — in parts. Any remainder goes home to the pool.
Voided or stale holds return funds automatically. Headroom restores itself.
Refunds never exceed what was captured — in parts, idempotently, and without inflating the agent's budget.
Eight invariants. Non-negotiable.
The platform is built so these cannot be broken — not by operators, not by agents, not by us.
Money is integer cents. Floating point never touches a balance.
The ledger is double-entry and append-only. Every journal sums to zero.
Audit history is immutable. Inserts only — updates and deletes are refused at the database itself.
Everything that moves money is idempotent. Replays return the original result, never a duplicate.
Cards never reload. Caps are fixed at issuance; spending power is replenished at the pool, under mandate.
No processor lock-in. The core never talks to a payment processor directly — every integration must pass the same conformance contract.
The agent is never the accountholder. Every instrument chains to a verified human principal.
An authorization is one atomic decision. Checks, journal, and record commit together — or none of them do.
Building agents that need to move money?
We're selecting a small set of design partners. Tell us what yours needs to do with money — we'll show you what safe looks like.
Thanks — you're on the list.
We'll be in touch soon.
Early partners work directly with the founding team — and shape the SDK before it ships.