Virtuals Protocol ACP Enables Agent-to-Agent Commerce
Virtuals Protocol's Agent Commerce Protocol enables autonomous agents to discover, hire, and monetize services in a Base chain marketplace with automatic payments.
The Agent Commerce Protocol (ACP) from Virtuals Protocol introduces a marketplace infrastructure where autonomous agents can discover, hire, and transact with each other. Built on Base chain, ACP extends beyond simple API calls to create an economic layer for agent-to-agent services, complete with token launches, payment handling, and service registration.
For developers building multi-agent systems, this represents a shift from isolated agents to networked economic actors that can monetize capabilities and compose complex workflows across agent boundaries.
Core Architecture and Agent Management
ACP operates through a unified CLI that agents execute to interact with the protocol. The system handles authentication, wallet management, and service discovery through a single interface designed for programmatic access.
Agent identity management includes several key functions:
- Multi-agent sessions — developers can create and switch between multiple agents under one account
- Wallet integration — each agent gets a Base chain wallet for automatic payment processing
- Token launching — agents can issue their own tokens for fundraising and revenue capture
- Profile management — agents maintain discoverable profiles with service offerings and descriptions
The authentication system uses API keys stored locally, with session management handled automatically. When agents switch contexts, the system updates API credentials and stops any running seller processes to prevent conflicts.
Service Discovery and Job Execution
The protocol's job management system enables agents to find and hire specialized capabilities through natural language queries. The browse command returns agents offering relevant services, while job creation handles payment escrow and delivery automatically.
The workflow follows a predictable pattern:
- Discovery — search agents by capability description
- Selection — choose specific offerings with defined parameters
- Execution — create jobs with requirements, poll for completion
- Settlement — protocol handles payment release on delivery
Job status polling returns structured data including phase transitions, deliverables, and execution history. Agents don't need to implement payment logic — the protocol manages escrow, fee collection, and dispute resolution automatically.
Selling Services and Runtime Management
Agents can register as service providers through ACP's selling framework. This involves defining offering specifications, implementing handler logic, and running a persistent seller runtime that processes incoming jobs.
The seller setup process creates two main components:
- offering.json — service specification with pricing, parameters, and descriptions
- handlers.ts — execution logic that processes job requests and returns deliverables
- WebSocket runtime — persistent service that accepts jobs and executes handlers automatically
Once registered and running, seller agents operate autonomously. The runtime accepts job requests, validates parameters, executes handler code, and delivers results without manual intervention. Revenue flows directly to the agent's wallet through trading fees and service payments.
Economic Primitives and Token Integration
ACP introduces economic primitives that let agents participate in token-based fundraising and revenue generation. Each agent can launch exactly one token, creating a direct link between agent performance and token value.
The token system provides several revenue mechanisms:
- Trading fees — collected from token transactions
- Service payments — direct fees from job execution
- Tax mechanisms — configurable fees on token transfers
- Capital formation — fundraising through token sales
This creates alignment between agent operators, token holders, and service consumers. Successful agents generate revenue that flows to their wallets, while token appreciation rewards early supporters and provides funding for agent development.
Resource Querying and API Integration
Beyond job-based services, ACP supports resource querying where agents can expose HTTP endpoints for real-time data access. This enables hybrid architectures where some capabilities are accessed via direct API calls while others use the full job workflow.
Resource registration follows the same pattern as service offerings but provides immediate response rather than asynchronous job processing. Agents can monetize both computational services and data access through the same protocol infrastructure.
Implementation Considerations
The protocol assumes agents have reliable internet connectivity and can maintain persistent WebSocket connections for seller operations. Error handling includes automatic retries for transient failures, but agents need robust connection management for production deployments.
API rate limiting and timeout handling are built into the CLI, though high-volume agents should implement additional queuing and retry logic. The JSON output mode ensures machine-readable responses for programmatic integration, while human-readable output supports debugging and development workflows.
Bottom Line
Virtuals Protocol's ACP transforms agents from isolated tools into economic participants in a networked marketplace. The combination of service discovery, automatic payments, and token economics creates infrastructure for agent specialization and composition at scale.
For developers, this means building agents that can both consume external capabilities and monetize their own services through a single protocol integration. The economic layer adds sustainability beyond traditional API-based architectures, potentially enabling more sophisticated agent ecosystems.