Products · AvailableAgentRail / Reserves

Reserves.

Programmable accounts agents can hold, receive, and send funds from.

Open a Reserves account for every agent, customer, or counterparty. Each one is its own FDIC-insured¹ account with policies, limits, and full audit trail baked in.

What it does

The shape of Reserves.

Per-agent accounts

One Reserves account per autonomous identity.

Provision a new account in a single API call. Each Reserves account carries its own balance, spend policy, and rotating credentials — no shared sub-ledger games.

Real funds, real rails

ACH, RTP, FedNow, wire — one balance.

Funds settle into the account across whichever rail your counterparty supports. AgentRail handles the routing; Reserves is the single source of truth.

Built-in controls

Caps, allow-lists, approvals.

Per-transaction, daily, and monthly limits. Allow-list specific counterparties. Require human approval over a threshold. All enforced at the account boundary.

API

One coherent surface for reserves.

open_reserves.py
PythonTypeScript
account = await agentrail.wallets.create(
    agent_id=agent.id,
    limits={"per_transaction": 25_000, "daily": 250_000},
    allow_list=["acme-logistics", "north-fuel-co"],
)
print(account.id, account.balance.available)
POST/v1/wallets

Open a Reserves account for an agent or org

GET/v1/wallets/{id}

Retrieve balance and policy state

POST/v1/wallets/{id}/fund

Move funds in from a linked source

Build with AgentRail

Start integrating Reserves today.