AgentPay Logo AgentPay
Documentation Initialize Agent
Logo AgentPay
Documentation Initialize Agent

Set it once. Pay on a schedule.

Recurring agent-to-agent payments. Choose amount, interval, and optional budget or run limit. The system pays on time — until you pause, cancel, or the order ends.

Initialize Agent How it runs

Standing Orders

Pay on a beat.
Not on a click.

An agent opens a standing order once. The ledger keeps sending the same amount on the same interval until the order ends, pauses, or hits its limits.

Recurring from → to Interval Budget-capped

Rhythm

One open. Many runs.

The order lives on the agent. Every interval the runner debits the sender, credits the receiver, and advances the counters.

t0

Open

Amount, interval, TTL and optional budget are fixed.

+1

First run

Ledger moves the amount. runs_done becomes 1.

+n

Next beats

Same path, same amount, until a limit is hit.

end

Stop

Max runs, budget, TTL, pause or cancel closes it.

Bounds

You set the ceiling. The runner respects it.

Standing orders never run forever by accident. Every open call can carry hard stops.

interval_sec
30 s – 30 d. How often the debit fires. Default one hour.
max_runs
Optional count. Order completes when runs_done reaches the limit.
budget_usd
Optional spend ceiling. Stops when spent_usd would exceed the budget.
ttl_seconds
Lifetime-to-live. Default 72 h. After expiry the order is closed automatically.
pause · resume
Live control. Freeze the next beats without cancelling. Resume continues from the schedule.

Lifecycle

Five states. No grey area.

The order is always in exactly one state. Dashboard and API use the same words.

active
Runner will fire the next beat
paused
Frozen. Resume continues the schedule
completed
max_runs or budget reached cleanly
cancelled
Owner stopped it early
expired
TTL ended. No more debits

Safety

Every beat still passes the gates.

A standing order is not a bypass. Each scheduled debit is checked the same way a one-shot pay is.

Wallet lock respected Velocity windows apply Daily cap still counts Policy allow / deny lists

If the agent is locked or over limit, that beat fails cleanly. The order stays active and waits for the next interval — or you pause it.

Telemetry

Everything the order remembers.

Each standing order carries its own counters. You always know how many times it has run, how much it has spent, and when the next beat is due.

API

Four verbs. One schedule.

Open once. Pause or resume when needed. Cancel when the subscription is done.

POST /api/standing/open
Create the order — amount, interval, TTL, optional max_runs and budget.
POST /api/standing/pause
Freeze upcoming beats. Counters and schedule stay intact.
POST /api/standing/resume
Start the runner again from the next due time.
POST /api/standing/cancel
Close the order permanently. No further debits.

Standing

Set the interval. The ledger keeps the beat.

Open once. Pause when you need to. Cancel when the subscription ends.

Open AgentPay

Now

The ledger is open.

Bind a repo. Send a POST. Agents settle — humans stay out of the way.

Join AgentPay

│

Join now
AI Assistant