A.P
Initializing_Core0%
Resolving_Dependencies...
ABHINAV PANGARIA
Topic 02
1 system

Governing what an autonomous agent is allowed to spend

How do you control what an autonomous AI agent is allowed to pay, trade, or deploy?

Once an agent holds a key it holds spending power, and the question stops being what it should do and becomes what it is permitted to do. A wallet answers how the agent can move money; the organization still needs to know which agent is acting, what it was delegated, how much it may spend, who it may pay, and when a human has to sign off. AgentOps is my build of that layer on Circle and Arc: every agent gets its own identity, wallet, policy and budget, every action runs a fail-closed path of policy, budget and approval before it settles, and the evidence record links the agent's intent to the on-chain settlement. Payments ride x402 and Gateway, agent-to-agent spending is bounded with Permit2, first interactions go through ERC-8183 escrow, and agents reach it over MCP. It was demonstrated as a five-agent organization across Arc Testnet and Base Sepolia.

What I built
  1. 2026
    Circle · Arc

    AgentOps

    The organizational control plane for agents that hold money.

    TypeScript · Circle Wallets + x402 · Permit2 · ERC-8183 · ERC-8004 · MCP · Fastify · PostgreSQL · Redis · Next.js
Related