x402 merchant
Public-url-checkUrl-verificationUrl-digestHttp-statusSha256

Public URL verification API for AI agents. Independently fetch one public HTTP(S) URL and return target HTTP status, final URL, raw response-body SHA-256 content fingerprint, content type/encoding, byte length, and UTC observation time. Use for URL integrity verification, website change detection, content fingerprints, and web evidence. Receipt v2 hashes content-encoded bytes without application decompression; 1 MB max, one 7-second fetch deadline, max three redirects, ports 80/443 only.

Not yet indexed

Sweeping the chain

We hold no settlements for this wallet. That is not the same as it having none, so we are looking: Queued. A worker will pick this up in a few seconds.

Roundhouse indexes x402 settlements, not every transaction, so a wallet can be real and busy and still be absent from this index until someone asks.

MerchantReport

0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1

0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1Explorer
$0.00
Received
$0.00
Paid out
0
Settlements
0
Distinct counterparties
In the 0 settlements scanned

Received $0.00 of the $716.80K Roundhouse has indexed across 25,178 wallets.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

Data quality

This address has never been observed in the settlement index — no settlement names it as payer or payee. Nothing has been assessed about it: this is an absence of data, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
No settlements observed yet

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent: it will check 0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1's payment record before paying it over the free read API. No key, no account.

GET api.roundhouseai.io/v0/merchants/0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1

Open skill.md
Show the prompt
Using Roundhouse, tell me whether this x402 merchant is worth paying: how many distinct
agents have paid it, how recently, and for what.

  Merchant wallet: 0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1

curl -s 'https://api.roundhouseai.io/v0/merchants/0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1'
curl -s 'https://api.roundhouseai.io/v0/entities/0xe9bd66143455134d3f11e1ecd67e47be3f74fdd1/settlements?limit=50'

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://preview.roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://preview.roundhouseai.io/skill.md first — it is the whole procedure.