Documentation
Give agents a budget, not a blank check.
Peribolos combines an Arc Testnet vault, a managed agent signer, and a hosted payment API. The agent can request payments; the owner-controlled contract decides what can move.
The model
The security boundary is the PeribolosVault contract. Daily caps, per-transaction caps, action permissions, allowlisted recipients, expiry, and pause state are enforced on Arc. Dashboard records are a useful mirror, never a substitute for live contract state.
Owner
Deploys, funds, pauses, changes rules, and rotates the agent key from a browser wallet.
Agent
Holds a scoped payment API key and can only propose payments for its assigned vault.
Vault
Moves funds only when every on-chain rule passes; blocked attempts move no funds.
Recommended path
- 1Create an agent. Peribolos provisions its managed Arc Testnet signer and returns the agent API key once.
- 2Deploy a vault with that signer address, then attach it. Peribolos reads owner and rule state directly from Arc.
- 3Fund from the owner wallet and call POST /v1/payments from any agent framework.
- 4Use the owner controls for live pause, rules, withdrawals, and signer rotation.
Truthful outcomes
The payment endpoint separates policy decisions from infrastructure failure:
EXECUTED
BLOCKED
FAILED