reins.yaml describes the accounts, refill budget, and transaction types you want the agent to use. Generate it with init --testnet-accounts so the addresses come from fresh accounts rather than copying example addresses.
Version and network
The current policy schema usesversion: 1. The quickstart uses network: testnet. The schema also recognizes devnet and mainnet, but the CLI’s apply command refuses mainnet.
Account roles
accounts.vault, accounts.allowance, and accounts.agent are required, distinct XRPL classic addresses. Keep the addresses produced by initialization.
Optional accounts.watchdog and accounts.agentKey must be supplied together. They must also be distinct from each other and from the three required accounts. See the account model before using that topology.
Refill budget
For XRP, use a positive decimal string with at most six fractional digits:amount caps each refill Check. period controls its lifetime and accepts an integer followed by s, m, h, d, or w. It is not a rolling spend window.
The schema also accepts issued assets as an object with currency and issuer. A currency code alone does not identify an issuer. This introductory workflow uses XRP to keep account setup and exposure easier to inspect.
Delegated transaction types
Choose the smallest set the workflow needs. For payment preparation:Payment, CheckCash, and EscrowFinish. The parser requires a nonempty permission list and rejects disallowed transaction types. A tool being present in the MCP server does not grant that transaction type on the ledger.
Permission Delegation restricts types rather than the amount of each transaction. Read enforcement before treating a permission list as an amount policy.
Limits that are not enforced yet
The parser acceptslimits.maxPerTx, limits.dailyVelocity, and limits.payees. They describe future independent co-signer rules. They are validated and reported, but the policy service needed to enforce them has not shipped.
Do not rely on these fields to protect funds in the current alpha.
Review before applying
After editing a policy, inspect the plan before submitting anything:verify to compare the intended policy with live ledger state. See the CLI reference for options.