AMP — Autonomous Machine Payments

Persistent payment channels for AI agents on Solana.

Why AMP

• Persistent channels replace per-request payments. Open a channel once, consume services freely. No per-call payment latency, no per-call on-chain transactions.
• Zero per-call friction. After channel open, requests carry only a channel reference and sequence number. The server verifies off-chain and meters locally.
• Solana native. 400ms finality, sub-cent settlement costs, SPL tokens. ~3 on-chain transactions instead of 1,000 for 1,000 API calls.

Quickstart

Server (Express):

import { AMP } from "@valeo/amp-server";

app.use(AMP.middleware({ rate: "0.001/call" }));

Client (Agent):

import { AMPClient } from "@valeo/amp-client";

const amp = new AMPClient({
  wallet: agentKeypair,
  budget: 10.0,
  token: "USDC",
});

const res = await amp.fetch("https://api.example.com/v1/data");

Ecosystem

• MCP Transport — native support for paid AI agent tool calls via JSON-RPC. Per-tool pricing, automatic channel management.
• Service Registry — on-chain directory of AMP-enabled services. Agents discover services by category, price, and reputation.
• Multi-Channel Netting — Stratum integration batches settlements across all channels in a netting cycle. 60-80% fewer on-chain transactions at scale.
• On-Chain Reputation — deterministic trust scores derived from channel history. No oracle, no subjective rating. Enables tiered pricing.
• Channel Chaining — agent supply chains. A service forwards upstream channel budget to downstream services, creating value chains that settle in one cycle.

Documentation

• Protocol Specification — full technical spec with on-chain architecture, message formats, and transport bindings
• Protocol Comparison — AMP vs x402 vs MPP with cost and latency analysis
• Diagrams — channel lifecycle, settlement flow, and architecture diagrams
• Examples — TypeScript examples for server and client integration

Deployments

Status

v0.2 — Deployed to Mainnet and Devnet

License

MIT

Built by

Valeo