RailPayDocs
Sandbox. No real funds move and nothing settles on a chain yet. What this means

Guides

AI agents

Give an agent its own wallet, inside limits you set.

Create an agent

POST /v1/agents creates the agent and returns its first agent key. The key is shown once; only a hash is stored. Fund the agent from your account with POST /v1/agents/:id/fund, and withdraw what is left with /withdraw.

Policy

FieldDefaultWhat it does
per_request_max0.05 SUSDLargest single payment the agent may make.
daily_cap5 SUSDTotal the agent may spend per UTC day.
allowed_hosts[] (any)Hosts the agent may pay. Empty means any host.
allow_a2afalseWhether the agent may pay other agents.
pausedfalseBlocks every payment while true.

Events

Every payment attempt is logged as paid or blocked. Blocked reasons: paused, over_per_request, over_daily_cap, host_not_allowed, a2a_not_allowed, insufficient_funds. Read them with GET /v1/agents/:id/events or on the agent page.

What an agent key can do

Agent keys can only call /v1/agent/* (pay and send) and are always bound by the agent's policy. They cannot touch the owner account.

The RailPay app runs in Sandbox mode. Balances are in Sandbox USD (SUSD). No real funds move and nothing settles on a chain. Chains, stablecoins, card issuing, ramps, fees and yield are TBD.

© 2026 RailPay. Built as practical payment infrastructure, not a token or fundraising project.