←All use cases

Pay With Locus · USDC wallets on Base

Agent-to-Agent Payments

Enable AI agents to pay each other for services, data, and compute — powering multi-agent swarm architectures and autonomous agent economies.

Updated

The rise of multi-agent systems

Modern AI architectures are moving beyond single-agent designs toward multi-agent swarms. Frameworks like OpenAI's Swarm, CrewAI, LangGraph, and AutoGen enable teams of specialized agents — a researcher, a coder, a reviewer, a deployer — working together on complex tasks. But when these agents need to exchange value, the infrastructure falls apart. How does a coding agent pay a testing agent for verification? How does an orchestrator allocate budget across a swarm of sub-agents? Agent-to-agent payments are the missing layer that makes true multi-agent collaboration possible.

How agent-to-agent payments work on Locus

Each agent gets its own wallet

Every agent in your swarm receives a non-custodial ERC-4337 smart wallet on Base, funded with USDC. The orchestrator can create wallets for sub-agents programmatically and allocate budgets to each one.

Direct wallet-to-wallet transfers

Agent A can send USDC directly to Agent B's wallet address. Transfers settle instantly on Base with near-zero gas fees. No intermediary approval needed — just policy checks against the sender's spending rules.

Budget delegation

An orchestrator agent can delegate a portion of its budget to specialist agents. Each sub-agent operates within its allocated budget, and the orchestrator retains full visibility into spending across the swarm.

Policy-enforced transactions

Every agent-to-agent transfer passes through Locus's three-layer policy engine. You can set per-transfer limits, restrict which agents can send to which, and cap total inter-agent spending per time period.

Multi-agent workflow examples

  • •Research swarm — An orchestrator delegates $5 each to three research agents. Each agent searches the web via Tavily, calls LLMs for summarization, and returns findings. The orchestrator pays a synthesis agent to compile the final report.
  • •Code review pipeline — A coding agent writes code, pays a testing agent to run it in a sandbox via Judge0, and then pays a review agent to audit for security issues. Each agent has its own budget and audit trail.
  • •Content production — A planning agent pays a writing agent to draft content, an image generation agent to create visuals via Stability AI, and an SEO agent to optimize the final output.
  • •Trading system — A market analysis agent purchases financial data from CoinGecko and Alpha Vantage, pays a prediction agent to run models, and forwards recommendations to an execution agent.

Why USDC on Base is ideal for agent-to-agent payments

Agent-to-agent payments need to be fast, cheap, and denominated in a stable currency. USDC on Base delivers all three: transactions settle in under two seconds with gas fees under $0.01, and USDC targets $1, though its market price can vary. Agents should still account for network fees, settlement conditions, and asset risk. This makes USDC the natural unit of account for autonomous agent economies.

Related resources

Frequently asked questions

Can one AI agent pay another AI agent directly?

Yes. Agent A can send USDC straight to Agent B's wallet address on Base. The transfer only has to pass the sender's spending rules.

How does an orchestrator give sub-agents a budget?

The orchestrator can create wallets for sub-agents in code and allocate a budget to each one. Each sub-agent spends within its allocation, and the orchestrator sees spending across the swarm.

Can I stop agents from paying each other too much?

Yes. Every agent-to-agent transfer is checked by the Locus policy engine. You can set per-transfer limits, restrict which agents can send to which, and cap total inter-agent spending per time period.

Which multi-agent frameworks does this work with?

Examples include OpenAI's Swarm, CrewAI, LangGraph, and AutoGen. Each agent in the team gets its own Locus wallet.