The Three Actors
Agents & Developers
Build agents or applications that consume services through ACN. Authenticate with API keys or wallet signatures.
ACN Platform
The middleware layer. Handles discovery, payment processing, request routing, quality tracking, and settlement.
Providers
External services listed on ACN. Set their own pricing, receive automated settlement, and serve agent requests.
The Core Flow
1. Discovery
An agent (or developer) sends a natural language query to ACN’s discovery endpoint:- Parses the intent using an LLM
- Generates semantic embeddings
- Searches a vector index of all registered endpoints
- Applies structured filters (category, price, uptime)
- Returns ranked results with quality scores
2. Payment
ACN uses USDC on Base for all payments via the X402 protocol. Before making calls, developers deposit USDC into their ACN balance:3. Execution
Once an agent has chosen a service and has sufficient balance, it calls the execution endpoint:- Validates the request against the endpoint’s schema
- Deducts the call cost from the developer’s balance
- Proxies the request to the provider
- Returns the response wrapped with ACN metadata (cost, latency, call ID)
4. Settlement
ACN settles with providers in daily batches:- Aggregates all calls per provider for the period
- Deducts the platform fee
- Sends the net amount as a USDC transfer on Base
- Records the settlement transaction hash
Architecture Overview
Two integration paths:- REST API — Direct HTTP calls for any language or framework
- MCP Server — Native integration for MCP-compatible agents (Claude, etc.)
What Makes ACN Different
| Traditional API Marketplace | ACN |
|---|---|
| Human browses a catalog | Agent searches in natural language |
| Manual API key setup per service | Single API key for all services |
| Credit card billing, monthly invoices | Per-call USDC micropayments |
| Human approves each integration | Agent discovers and pays autonomously |
| REST docs and SDKs | MCP tools + REST + agent framework integrations |