Arc Testnet live Vault source verified Inspect deployment
00 Spend control for autonomous capital

Autonomy
needs a ceiling.

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.

Chain
Arc L1
Settlement
USDC
Custody
None
Policy
On-chain

Wallets were built for humans. Agents inherited the keys.

A wallet knows balance.
It does not know intent.

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.

A / 01

Runaway loop

The agent retries until the balance is gone. Spend scales with model error.

Contained by INV-M6 → INV-2 → INV-3
A / 02

Wrong payee

A hijacked prompt routes USDC to an address nobody approved.

Contained by allowlist + payee binding
A / 03

Stale delegation

After re-authorization, old signatures still look cryptographically valid.

Contained by INV-6 / epoch bump

Deterministic checks. No model in the trust path.

The agent proposes.
The vault disposes.

Three checks stand between intent and settlement. Each one is deterministic; none depend on the model behaving.

01dryRun()

Simulate

Resolve allowlist, counterparty score, tier band, and rolling allowance before a signature exists. Ambiguity halts.

no capital moves
02signVoucher()

Sign

A cumulative EIP-712 voucher binds agent, merchant, token, amount, expiry, and epoch. The prompt leaves only as a hash.

replay-resistant
03claimVoucher()

Settle

The vault re-checks the delta on-chain: monotonic, bounded, inside the rolling 24h ceiling, under the active epoch.

fee at source
VoucherTypes.sol
struct Voucher {
  address agentKey;
  address merchant;
  address token;
  uint256 cumulativeAmount; // never per-call
  uint256 validUntil;
  uint64  epoch;            // INV-6
  bytes32 memo;             // intent hash
}
PROTOCOL_VERSION = "3" EIP-712
01

Policy is bytecode, not copy

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.

02

Intent stays local

keccak256(prompt || timestamp) travels in the voucher memo. The raw prompt never crosses the trust boundary.

03

YOPO for streams

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.

Enforced,
not advised.

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()
36Foundry cases
10,000invariant runs in CI
277SDK tests across TS + Python
0custody paths

One control plane. Two rails. Never a competing bridge.

We don't move the rail.
We decide who may use it.

Paythos merchants settle through the vault. Circle marketplace services settle through Circle. The same GOFER gate runs before either signature.

Rail 01 vault-settled

Paythos merchant

x402 challenge → policy gate → cumulative voucher → claimVoucher(). Deltas, expiry, allowlist, and epoch are re-checked on-chain.

ClientMiddlewareVault
  • Non-custodial reserve
  • Fee deducted at source
  • Monotonic batch settlement
Rail 02 circle-native

Agent Marketplace

Standard x402 v2 → GatewayWalletBatched or exact EIP-3009 → Circle settlement. Paythos selects only Arc USDC and gates every authorization before it exists.

ClientGOFERCircle
  • Same allowlist and tier gate
  • Direct spend tracked client-side
  • No vault custody for the rail

Cross-chain funding uses Circle CCTP only. Paythos does not build, operate, or hide a bridge.

Arc Testnet. Real transactions. No mock ledger.

Shipped to testnet.
Not a deck.

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-09
LIVE DEPLOYMENT / ARC TESTNET source verified
PaythosVault
Settlement token native USDC · 0x3600…0000
Fee 150 bps · deducted at source
Owner 0x7D6d…Fb2C
Every claim above is reproducible from the repository. Review the harnesses

Bring the agent you already run.

A guardrail,
not a migration.

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.

TypeScript SDK

Strict ESM client, cumulative voucher signer, x402 v2 negotiation, YOPO streams.

@paythos/sdk

Python SDK

Pydantic mirrors, FastAPI middleware, async flush daemon, parity tests.

paythos

MCP server

stdio daemon with four tools. Environment-only config; no config code touched.

paythos-mcp

LangChain

DynamicStructuredTool wrappers for budget, dry-run, and purchase.

makeLangChainTools()

ElizaOS

Action validate/handler pair plus plugin export.

paythosPlugin

AutoGen · CrewAI

OpenAI function specs and dispatch on TS; CrewAI tools on Python.

functionSpecs()

The remaining work is integration, not invention.

From testnet
to a funded pilot.

A milestone-based grant extends the deployed core into cross-chain funding, a design-partner pilot, and a public SDK release on Arc.

  1. done
    Arc Testnet coreVault, source verification, funded settlements, Circle signer.
  2. next
    CCTP funding pathBurn on source chain → Circle attestation → mint on Arc → deposit.
  3. next
    Agent Wallet approval adapterCircle Agent Wallets approval and audit surface.
  4. next
    Design-partner pilotTwo to three merchants with real services and spend policies.
  5. blocked
    Arc Mainnet readinessUSDC address confirmation, deployment, verification.
  6. next
    Public SDK releaseVersioned TypeScript and Python packages with docs.
08 Technical review

Put a ceiling
on agent spend.

Review the vault, run the invariant suite, or bring a design-partner workload to the Gate 5 pilot.

Review the repository Read the invariants Grant dossier and architecture brief available on request.