Runaway loop
The agent retries until the balance is gone. Spend scales with model error.
INV-M6 → INV-2 → INV-3
Paythos is the non-custodial guardrail between an AI agent and its USDC. Daily limits, per-transaction caps, and human review are enforced in vault bytecode on Arc L1 — not in a system prompt.
Wallets were built for humans. Agents inherited the keys.
Give an agent a key and you have given it the ability to spend. The model decides what is reasonable; the wallet has no opinion. That gap is where recursive loops, wrong payees, and stale delegations become losses.
The fix is not a better prompt. It is a smaller blast radius.
The agent retries until the balance is gone. Spend scales with model error.
INV-M6 → INV-2 → INV-3
A hijacked prompt routes USDC to an address nobody approved.
allowlist + payee binding
After re-authorization, old signatures still look cryptographically valid.
INV-6 / epoch bump
Deterministic checks. No model in the trust path.
Three checks stand between intent and settlement. Each one is deterministic; none depend on the model behaving.
dryRun()Resolve allowlist, counterparty score, tier band, and rolling allowance before a signature exists. Ambiguity halts.
no capital movessignVoucher()A cumulative EIP-712 voucher binds agent, merchant, token, amount, expiry, and epoch. The prompt leaves only as a hash.
replay-resistantclaimVoucher()The vault re-checks the delta on-chain: monotonic, bounded, inside the rolling 24h ceiling, under the active epoch.
fee at sourcestruct Voucher {
address agentKey;
address merchant;
address token;
uint256 cumulativeAmount; // never per-call
uint256 validUntil;
uint64 epoch; // INV-6
bytes32 memo; // intent hash
}
Deltas are settled against the vault's own state. The client cannot raise its own ceiling, skip a check, or talk the merchant into a larger claim.
keccak256(prompt || timestamp) travels in the voucher memo.
The raw prompt never crosses the trust boundary.
Metered streams hold only the ceiling. The client signs exact consumption at completion — and signs nothing when the stream fails.
Six properties the vault cannot be argued out of.
Every guard maps to a revert selector and a test. The table below is the public contract between the agent and the capital.
Read the full security model| ID | Invariant | Enforcement |
|---|---|---|
| INV-1 | Monotonic cumulative claim per (agent, merchant, epoch). | InvalidVoucherAmount() |
| INV-2 | Rolling 24h ceiling across 25 hourly slots. No oracle, no cron. | DailyLimitExceeded() |
| INV-3 | Per-transaction delta never exceeds maxPerTx. |
MaxPerTxExceeded() |
| INV-4 | Voucher and policy TTL are bounded by block time. | SessionExpired() |
| INV-5 | Only the owner exits capital; no pooled liquidity, yield, or delegatecall. | emergencyWithdraw / owner-only |
| INV-6 | Vouchers bind to the active delegation epoch. Re-authorization orphans stale signatures. | SessionEpochMismatch() |
One control plane. Two rails. Never a competing bridge.
Paythos merchants settle through the vault. Circle marketplace services settle through Circle. The same GOFER gate runs before either signature.
x402 challenge → policy gate → cumulative voucher → claimVoucher().
Deltas, expiry, allowlist, and epoch are re-checked on-chain.
Standard x402 v2 → GatewayWalletBatched or exact EIP-3009 →
Circle settlement. Paythos selects only Arc USDC and gates every
authorization before it exists.
Cross-chain funding uses Circle CCTP only. Paythos does not build, operate, or hide a bridge.
Arc Testnet. Real transactions. No mock ledger.
The current v3 vault is source-verified on Blockscout. Claims below are linked to the Arc explorer; amounts, fees, and epoch behavior are asserted in the harnesses that produced them.
PROTOCOL v3 · 2026-11-09native USDC · 0x3600…0000
150 bps · deducted at source
0x7D6d…Fb2C
0xa874d4f2…876c69
MCP + SDK settlement
Merchant net 0.0985 USDC
0x99a1c655…e536d668
Circle wallet signature
Same vouchers, external signer
0x6d18c951…9342eb
api.botpay.network/go
Bring the agent you already run.
Paythos ships as an SDK, a merchant middleware, and an MCP server. Existing agent stacks keep their tools; the spend path gains a policy boundary.
Strict ESM client, cumulative voucher signer, x402 v2 negotiation, YOPO streams.
@paythos/sdk
Pydantic mirrors, FastAPI middleware, async flush daemon, parity tests.
paythos
stdio daemon with four tools. Environment-only config; no config code touched.
paythos-mcp
DynamicStructuredTool wrappers for budget, dry-run, and purchase.
makeLangChainTools()
Action validate/handler pair plus plugin export.
paythosPlugin
OpenAI function specs and dispatch on TS; CrewAI tools on Python.
functionSpecs()
The remaining work is integration, not invention.
A milestone-based grant extends the deployed core into cross-chain funding, a design-partner pilot, and a public SDK release on Arc.
Review the vault, run the invariant suite, or bring a design-partner workload to the Gate 5 pilot.