← Back to Social Reports

Agent Merchant Signals Analysis

2026-02-27

Agent Merchant Signals Analysis

Date: 2026-02-27 Focus: (1) On-chain x402 transaction flows on Base + (3) MCP Server / Registry signals


1. ON-CHAIN x402 TRANSACTION ANALYSIS

Architecture (How x402 Settles On-Chain)

x402 uses two settlement paths on Base, both involving USDC:

PathContractHow It Works
EIP-3009USDC directly (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)Facilitator calls transferWithAuthorization() on USDC contract. Payer signs offline; facilitator submits the tx.
Permit2x402 Exact Permit2 Proxy (0x4020615294c913F045dc10f0a5cdEbd86c280001)Uses Uniswap's Permit2 standard via a dedicated x402 proxy contract. Newer, more universal (any ERC-20).

There's also an Upto Permit2 Proxy (0x4020633461b2895a48930Ff97eE8fCdE8E520002) for variable-amount payments — zero transactions to date.

CDP Public Facilitator Wallet

Address: 0x01e92b91b5669A5F3C889094d3e83Ce3487954B8 Balance: 0.0195 ETH (~$37.84) for gas Total transactions: 22 (as of Feb 27 16:30 UTC)

MetricValue
Total txs22
EIP-3009 (transferWithAuthorization)3 txs → USDC contract
Permit2 proxy calls20 txs → 0x4020...0001
First tx~Feb 26, 2026 03:26 UTC
Latest txFeb 27, 2026 04:35 UTC
Active period~25 hours
Unique callers1 (the facilitator itself)

x402 Exact Permit2 Proxy Activity

Address: 0x4020615294c913F045dc10f0a5cdEbd86c280001 Total transactions: 20 All transactions from: single facilitator address 0x01e92b91...3487954B8 Period: Feb 26-27, 2026 (all within last 36 hours)

Key On-Chain Findings

  1. Extremely early stage. 22 total facilitator transactions in ~25 hours. This is the CDP public facilitator — the one Coinbase runs for anyone to use. Traffic is minimal.

  2. Single facilitator monopoly. All on-chain settlement comes from one Coinbase-operated wallet. No evidence of third-party facilitators operating on Base yet.

  3. Permit2 path dominates. 20/22 txs use the Permit2 proxy (newer V2 path). Only 3 use the original EIP-3009 transferWithAuthorization path.

  4. Cannot attribute all EIP-3009 calls to x402. transferWithAuthorization on USDC is used by many protocols (Circle, Coinbase, custodians). We can only definitively attribute the Permit2 proxy txs to x402.

  5. Volume estimate. Without decoding each tx's USDC amount, and given service prices of $0.001–$0.10 per call, 22 txs likely represent < $2 total USDC volume through the CDP facilitator.

Caveat: What We Can't See

  • Self-hosted facilitators: Services like Zapper or Nansen could run their own facilitator, settling payments without going through the CDP public facilitator. These wouldn't show up in our analysis.
  • Testnet activity: Base Sepolia testnet usage is invisible to mainnet analysis.
  • Off-chain verification: Some services may verify payment signatures off-chain (checking balance + signature validity) without settling immediately, deferring settlement.

2. CDP x402 DISCOVERY REGISTRY

Registry Stats (Live as of Feb 27, 2026)

MetricValue
Total registered services12,973
Services 12 days ago (Feb 15)~100
Growth rate~130x in 12 days
NetworkPredominantly Base mainnet (eip155:8453)
Payment assetUSDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
Protocol versionsV1 (majority) and V2 (newer entries)
Solana support2 services (Nansen) — first multi-chain entries

Top Service Providers (from first 100 entries analyzed)

Provider# EndpointsCategoryPrice RangeQuality
Zapper (public.zapper.xyz)15Portfolio/Token/NFT/DeFi data$0.0011–0.0045⭐⭐⭐ Premium
lowpaymentfee.com~40+Generic financial data (stocks, crypto, carts)$0.02 flat⚠️ Likely auto-generated
x402.twit.sh10Full Twitter/X API proxy$0.0025–0.01⭐⭐⭐ Novel — replaces X API
httpay.xyz6DeFi tools, MEV scanner, gas tracker$0.005–0.02⭐⭐ Useful
aurracloud.com6Agent chat services$0.001–0.05⭐ Generic
Nansen (api.nansen.ai)2Smart money netflow, historical balances$0.01–0.05⭐⭐⭐ Premium
slinkylayer.ai3NLP, sentiment, spam detection$0.05⭐⭐
agentutil.net2Intent security, API docs lookup$0.002⭐⭐ Novel
x-router.ai1Text-to-image generation$0.0057⭐⭐
Recoup (recoup-api.vercel.app)2AI image generation$0.001–0.15⭐⭐
402box.io1Team contact/collaboration$0.01⭐ Niche
nftitem.io1PNG → blockchain NFT upload$0.10⭐⭐ Novel
genbase.fun1GPT Image-1 generation$0.02
evplus1Funding rate arbitrage signals$0.10⭐⭐

Notable New Entrants (vs. Feb 15 survey)

  1. x402.twit.sh — Full Twitter/X API replacement via x402. Search tweets, get user profiles, followers/following, all via micropayments. No API key needed. This is the model for x402 adoption — wrapping expensive/restricted APIs behind micropayments.

  2. Nansen — First major Web3 analytics platform on x402. Smart money tracking and historical balances. Also first to support Solana payments alongside Base USDC.

  3. agentutil.net — "Intent security" service — pre-flight safety checks before agent actions. Purpose-built for autonomous agents.

  4. nftitem.io — Upload PNG to blockchain and mint NFT, all via one x402 call. Agent-native content creation.

Service Ecosystem Health Assessment

The good:

  • 130x growth in 12 days shows massive developer interest
  • Zapper and Nansen give x402 credibility (real data from real companies)
  • Price range ($0.001–$0.15) is appropriate for micropayments
  • Twitter/X API replacement is a killer use case for agents
  • First multi-chain (Solana) support appearing

The concerning:

  • lowpaymentfee.com alone accounts for 40+ endpoints of questionable quality — inflates count
  • Many services are wrappers around free data (stock prices, crypto prices)
  • Several "joke" or demo endpoints still registered on mainnet
  • Only 22 on-chain settlements vs 12,973 registered services = 0.17% usage rate
  • No quality filtering or reputation system in the registry

The verdict: The x402 registry is in its "app store launch week" phase — lots of listings, very little actual usage. Quality will matter more than quantity.


3. MCP SERVER / CLAWHUB REGISTRY SIGNALS

ClawHub (from Feb 16 survey — latest available)

MetricValue
Total skills7,779
Payment/wallet skills20+ identified
CategoriesBrowser, API, Data, Finance, DevTools, etc.

Key payment-related skills identified:

  • Paylobster (agent payment processing)
  • 1ly (identity + payments)
  • AGIRAILS (agent commerce rails)
  • FluxA (financial automation)
  • Base Wallet (crypto wallet management)
  • Maton (payment orchestration)
  • Paytoll (payroll for agents)

Smithery.ai / mcp.so

Unable to access directly (Cloudflare/Vercel security blocks on both platforms). Data would need browser automation.

Known from secondary sources:

  • Smithery.ai is the leading MCP server registry
  • MCP server count growing rapidly with Claude Desktop and Cline adoption
  • Key agent-native MCP servers: Browserbase, Firecrawl, E2B, AgentMail, Composio

4. SYNTHESIS: WHAT THE DATA TELLS US

Transaction Volume Verdict

x402 on-chain volume is negligible. 22 transactions totaling likely < $2 in USDC through the CDP facilitator. This is an infrastructure that's been built but not yet adopted at scale.

However, the registry explosion (100 → 12,973 services in 12 days) signals massive developer anticipation. The protocol is in the "build it" phase, not the "they will come" phase yet.

Who's Actually Selling to Agents?

Based on the x402 registry data, the highest-signal merchants selling to AI agents are:

RankMerchantWhySignal Strength
1Zapper15 real endpoints, premium data, active development⭐⭐⭐⭐⭐
2x402.twit.shNovel use case (X API replacement), 10 endpoints⭐⭐⭐⭐
3NansenPremium analytics, first Solana support, real brand⭐⭐⭐⭐
4httpay.xyzMultiple DeFi tools, active builder⭐⭐⭐
5agentutil.netPurpose-built for agents (intent security)⭐⭐⭐
6Bitrefill(from our testing) Real purchases, no account needed⭐⭐⭐⭐
7nftitem.ioNovel: on-chain storage via micropayment⭐⭐⭐
8x-router.aiAI image gen via x402⭐⭐

Methodology Gaps

  1. No way to distinguish agent vs human API calls in aggregate metrics
  2. Self-hosted facilitators are invisible — Zapper/Nansen might settle payments internally
  3. No download/usage metrics in the CDP registry (unlike npm/PyPI)
  4. ClawHub doesn't expose download counts for skills
  5. MCP registries (Smithery, mcp.so) blocked — need browser automation session

Recommended Next Steps

  1. Decode the 22 facilitator txs to extract actual USDC amounts and recipient addresses (would reveal which services got paid)
  2. Monitor the facilitator wallet weekly — transaction growth rate is the key leading indicator
  3. Run a Smithery.ai scrape via browser to get MCP server popularity data
  4. Check npm download trends for @x402/fetch and @x402/evm packages — proxy for developer adoption
  5. Track new x402 service registrations — query discovery API daily and diff