DEV Community

Nathaniel Cruz
Nathaniel Cruz

Posted on

Circle Nanopayments runs on x402 — what this means for AI agents that pay for data

#aiweb3javascriptprogramming

Last week Circle shipped Nanopayments. The interesting part isn't the feature — it's what they built it on.

They chose x402.

Not a proprietary Circle API. Not a closed payment protocol. They built on the open HTTP standard that Cloudflare, Coinbase, and the x402 Foundation have been developing. That's a meaningful signal if you're building agents that buy things.

The agent payment rail race is settling

Quick recap of where things stand:

x402 — open HTTP standard. A server responds to an unauthorized request with 402 Payment Required, and the body tells the client exactly what to pay, to whom, and how. The client pays in USDC on Base, includes a signed payment proof in an X-Payment header, and gets the data. No API keys. No billing dashboard. The payment is the auth.

Stripe Tempo — enterprise billing for AI platforms. Designed for SaaS companies charging humans for AI features. Not designed for agent-to-agent micropayments at sub-cent scale.

Circle Nanopayments — just launched, built on x402. Sub-cent transactions at high volume. Agent-native.

The distinction matters: Stripe Tempo solves human billing. x402 solves machine billing. When Circle — the company that issues USDC — ships their agent payment product on x402, they're voting with their engineering budget.

Why open standards win payment rails

HTTP won over proprietary protocols. TCP/IP beat network-specific stacks. SMTP beat closed email systems. The pattern: when you need interoperability across organizations, open standards beat proprietary ones.

Agent payments are the same problem. An agent built by company A needs to pay a data endpoint run by company B without either side needing a prior commercial agreement. That only works at scale with a shared standard. x402 is that standard.

Stripe Tempo won't lose — it'll own the enterprise procurement layer. But the machine-to-machine payment layer is x402 territory, and Circle + Cloudflare + Coinbase backing it is close to consensus.

What this means for agents that pay for data

If you're building an AI agent that fetches live data — DeFi yields, token anomalies, security intelligence, market signals — x402 is the payment primitive to integrate now.

The flow is three steps.

Step 1: Hit a data endpoint, get a 402

curl https://clawmerchants.com/v1/data/defi-yields-live
# HTTP/2 402
Enter fullscreen mode Exit fullscreen mode

The 402 body tells the agent what to pay:

{
  "protocol": "x402",
  "payment": {
    "price": "0.005",
    "currency": "USDC",
    "chain": "base",
    "chainId": 8453,
    "recipient": "<provider-wallet>"
  }
}
Enter fullscreen mode Exit fullscreen mode

Step 2: Preview before buying

curl https://clawmerchants.com/v1/preview/defi-yields-live
Enter fullscreen mode Exit fullscreen mode

Free preview, no payment needed. The agent evaluates whether the data is relevant to its current task before spending anything. This matters for autonomous agents running on a budget.

Step 3: Pay with USDC on Base, include proof

import { ethers } from 'ethers';

const provider = new ethers.JsonRpcProvider('https://mainnet.base.org');
const wallet = new ethers.Wallet(process.env.AGENT_PRIVATE_KEY!, provider);

const usdc = new ethers.Contract(
  '0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913',
  ['function transfer(address to, uint256 amount) returns (bool)'],
  wallet
);

const tx = await usdc.transfer(RECIPIENT, ethers.parseUnits('0.005', 6));
const receipt = await tx.wait();

const paymentProof = Buffer.from(JSON.stringify({
  txHash: receipt.hash,
  buyerWallet: wallet.address,
  buyerAgentId: 'my-agent'
})).toString('base64');

const response = await fetch('https://clawmerchants.com/v1/data/defi-yields-live', {
  headers: { 'X-Payment': paymentProof }
});

const pools = await response.json();
// => 50 live DeFi pools with APY, TVL, chain, riskTier
Enter fullscreen mode Exit fullscreen mode

No API keys. No subscription. No rate limit negotiation. The whole flow is HTTP.

ClawMerchants: agent data feeds live on x402

ClawMerchants is an agent-native data and skills marketplace running on x402 from day one. Catalog includes:

  • defi-yields-live — top 50 risk-ranked DeFi pools from DeFiLlama ($0.005/query, 5min refresh)
  • token-anomalies-live — real-time price anomalies from CoinGecko ($0.01/query)
  • security-intel-live — live CVEs with CVSS scores from OSV.dev + NVD ($0.02/query)
  • market-data-live — BTC/ETH/SOL price + volume ($0.01/query)
  • crypto-sentiment-live — Fear & Greed Index + 7-day trend ($0.01/query)
  • Agent skills (SKILL.md protocols): security audit, code review, testing eval, workflow automation

Everything is USDC fractions. No subscriptions. The machine-readable catalog is at /.well-known/agent-catalog.json.

Circle building Nanopayments on x402 just validated the infrastructure these feeds run on. Agents using x402 today are already on the winning rail.

Try it 

# Free preview — no payment needed
curl https://clawmerchants.com/v1/preview/defi-yields-live

# Full agent catalog (machine-readable)
curl https://clawmerchants.com/.well-known/agent-catalog.json
Enter fullscreen mode Exit fullscreen mode

Browse the full catalog: clawmerchants.com/browse

Prior posts in this series:

Install ClawMerchants skills in Claude Code or Cursor:

# Install all skills
npx skills add danielxri/clawmerchants

# Install specific skills
npx skills add danielxri/clawmerchants --skill agent-security-audit-skill
npx skills add danielxri/clawmerchants --skill code-review-skill
npx skills add danielxri/clawmerchants --skill agent-testing-eval-skill
Enter fullscreen mode Exit fullscreen mode

Top comments (0)