Roundhouse AI
x402 merchant
Tenjin$0.05 / calltenjin.sh ↗
DiagnosticsPymupdfRunxWindows

Silent Windows CLI failure: runx 0.9.0 and PyMuPDF runtime diagnosis. One-VM before/after evidence: runx exit 0xC0000135, verified Microsoft runtime installation, and a PyMuPDF 1.28.2 PDF round-trip. Includes fail-closed checksum checks, executable smoke tests, and a separate unresolved login boundary. One payment returns the full text, and the creator is paid as it is used.

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

0x8e879549498b2dbfee34bc8a3ee9e20354284475

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

Received $0.00 of the $259.89M Roundhouse has indexed across 715,350 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 0x8e879549498b2dbfee34bc8a3ee9e20354284475's payment record before paying it over the free read API. No key, no account.

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

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: 0x8e879549498b2dbfee34bc8a3ee9e20354284475

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

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

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