DEV Community: Donny Nguyen (Donny Diamond Hands)

Your x402 API settled on mainnet but never showed up in Coinbase's Bazaar? Check one character.

Donny Nguyen (Donny Diamond Hands) — Thu, 30 Jul 2026 01:19:31 +0000

We run two pay-per-call x402 endpoints (cross-DEX market data, Uniswap v4 hook risk scans). We settled four real mainnet payments through the CDP facilitator over four weeks — and the Bazaar merchant endpoint kept returning:

{"pagination":{"limit":20,"offset":0,"total":0},"resources":[]}

We blamed "async index lag" for a month. It wasn't lag. It was one character — well, five: http://.

The diagnostic that costs nothing

Before you pay for another settle hoping the index "catches up", decode your own 402 challenge:

curl -sI https://your-api.example.com/paid-route | \
  grep -i payment-required | cut -d' ' -f2 | base64 -d | jq .resource.url

If that prints http://your-api... instead of https://, you have found your problem. CDP silently declines to index a resource whose resource.url isn't HTTPS. No error, no rejected status — the settle succeeds, your money moves, and the listing never appears.

Why it happens to almost everyone

You're behind a TLS-terminating proxy — Railway, Cloudflare, Render, Fly, a load balancer. TLS ends at the edge, so your Express app sees plain HTTP and req.protocol === 'http'. The x402 middleware bakes that protocol into resource.url in every 402 challenge and every settle payload.

The fix is one line, before you mount paymentMiddleware:

app.set('trust proxy', 1);

Use 1, not true. With true, Express takes the leftmost X-Forwarded-For entry — which any client can forge to dodge your rate limiter. With 1 it takes the proxy-observed entry, which can't be spoofed. We verified: 16 parallel requests with 16 forged X-Forwarded-For values still rate-limited correctly.

After deploying that one line, our very next settle indexed in under a minute. Four weeks of "lag", solved by one character of scheme.

Three more traps on the way to a listing

1. The 500-character description cap. The CDP facilitator hard-rejects any settle whose resource.description exceeds 500 chars — with a misleading schema-union error your buyer only ever sees as a silent second 402. We now assert the length at boot so it can't regress silently.

2. A price floor may exist. Our $0.001 route settled successfully and did not index in 30+ minutes. The same route at $0.01 indexed within four minutes of the next settle. Not conclusive (time passed too), but if your cheap route won't list, try a settle at ≥$0.01 before debugging anything else.

3. Probe traffic will impersonate demand. Within hours of listing, something started hitting our paid route at a machine-steady ~240 requests/hour — replaying the exact example input from our own discovery metadata. One User-Agent hash accounted for 94% of it. If you're counting 402 challenges as "interest", tag and exclude requests that replay your declared example, or your demand number is fiction.

Working examples

Both endpoints are live if you want a reference implementation to poke at:

https://x402.donnyautomation.com/call?pair=WBNB/USDC — cross-DEX prices, liquidity & arbitrage spread on BSC, $0.01
https://x402.donnyautomation.com/v4hooks?address=0x... — Uniswap v4 hook custody-risk decode on Base, $0.01
Free, no-payment demo: https://x402.donnyautomation.com/demo/v4hooks/0x000052423c1dB6B7ff8641b85A7eEfc7B2791888
Or install the MCP wrapper and let your agent pay for itself: npx bsc-dex-spread-mcp (npm: bsc-dex-spread-mcp)

Hit the 402, decode the header, and check that resource.url says https. Ours does now.

Give your AI agent a cross-DEX spread tool it pays for itself (x402 + MCP, no account, no key)

Donny Nguyen (Donny Diamond Hands) — Fri, 03 Jul 2026 23:52:48 +0000

AI agents are starting to pay for data directly. The x402 protocol lets an HTTP
endpoint answer a request with 402 Payment Required, the client signs a small
USDC payment, and the same request is retried and served. No signup, no API key
to request, no invoice — the agent just pays a cent and gets the data.

I put a real endpoint behind that protocol and wrapped it as an MCP tool. This
post covers what it returns, why an agent would want it, and how to plug it in.

What the endpoint does

The endpoint sells one thing: real-time cross-DEX price and spread data for
PancakeSwap v2 and v3 on BNB Smart Chain (BSC).

GET https://x402.donnyautomation.com/call?pair=WBNB/USDC

Given a token pair (SYM/SYM, first symbol is the USD-priceable side) and an
optional PancakeSwap v3 fee tier, it returns:

per-venue mid prices across PancakeSwap v2 and v3 pools,
the best buy and best sell venue,
the gross cross-DEX spread in basis points,
per-venue and total liquidity (TVL), and
the source block number.

A trimmed response:

{
  "pair": "WBNB/USDC", "network": "bsc", "chainId": 56,
  "blockNumber": 107562007, "nativeUsd": 546.6,
  "pricesByVenue": [ { "venue": "pancake", "surface": "v2", "price": 546.6, "tvlUsd": 1234567 }, ... ],
  "bestBuy":  { "venue": "pancakeV3:500", "price": ... },
  "bestSell": { "venue": "biswap",        "price": ... },
  "midSpreadBps": 27.4,
  "crossDex": { "grossSpreadBps": 14.05, "buyVenue": "...", "sellVenue": "...", "surface": "v2v3" },
  "liquidity": { "venues": 7, "totalTvlUsd": ... },
  "ts": "2026-07-01T...", "source": "rpc"
}

It costs $0.01 USDC per call on Base mainnet. The seller holds no private
key — payment settlement is handled by a facilitator, and the endpoint only
proxies to its BSC reader once payment is verified.

Why an agent needs cross-DEX spread data

Cross-DEX spread is the raw signal behind several agent tasks:

Arbitrage detection — a positive gross spread across venues, net of fees, is the entry condition for a two-leg trade.
Best-execution routing — which venue to buy from and which to sell to, right now, at this block.
Slippage and liquidity checks — per-venue TVL tells an agent whether a given size will move the price.

The alternative is for every agent to run BSC RPC infrastructure, maintain pool
addresses across v2 and v3 fee tiers, and re-derive constant-product and
concentrated-liquidity math. Most agents should not. One tool call, one cent, a
fresh block-stamped answer.

Using it from an MCP client

The endpoint is wrapped as a Model Context Protocol server so any MCP-capable
agent (Claude Desktop, Claude Code, and others) can call it as a tool. Install:

npm install -g bsc-dex-spread-mcp

It is also available via Smithery
and the official MCP registry (io.github.donnywin85/bsc-dex-spread).

Then add it to your MCP client config, supplying your own buyer wallet:

{
  "mcpServers": {
    "bsc-dex-spread": {
      "command": "npx",
      "args": ["-y", "bsc-dex-spread-mcp"],
      "env": { "EVM_PRIVATE_KEY": "0xYOUR_BASE_MAINNET_BUYER_KEY" }
    }
  }
}

A note on the wallet model, because it matters: you supply the key; the package
ships none. The server signs each payment with the key in EVM_PRIVATE_KEY,
which you set in your own config. Fund that wallet with a few dollars of USDC on
Base and nothing else — the x402 exact scheme uses EIP-3009
transferWithAuthorization, so the facilitator broadcasts the transfer and pays
the gas. A zero-ETH wallet settles fine. Treat it as a disposable, low-balance
spending wallet.

Once configured, the agent has a get_dex_spread(pair, fee?) tool and pays
$0.01 USDC each time it calls it.

Proof it is live

Live usage/telemetry page: https://x402.donnyautomation.com/stats
First real mainnet settlement (self-payment, to prove the path end to end): 0x0c3ceda02f8aa36d48da392330e5bdcc9f34632a5dba2366a1663d6e7a301733 — Base mainnet, receipt status success. The transaction was submitted by the facilitator, confirming the buyer paid zero gas.

The /stats page shows challenge-versus-paid counts and recent settlements, so
you can watch real demand accrue rather than take my word for it.

Takeaway

If you are building agents that touch on-chain markets, this is a small, honest
example of the pattern worth copying: a narrow, useful data endpoint, priced per
call, discoverable and payable by machines without a human in the loop. The
protocol is x402; the packaging is MCP; the price is a cent.