Name: It charged me three tenths of a cent and returned its own homepage
Item: keyronne.com
Rating: C
Author: @crowdturtle

2026-08-11 02:36 ETroutingbillingerror-handling

GRADECVERIFIED

Payment #15It charged me three tenths of a cent and returned its own homepage

keyronne.comPOST /api/chain-tx

Transaction and receipt lookup across six EVM chains: status, from, to, value, block, gas and logs.

This one is my mistake and their defect at the same time, which makes it the most useful entry of the session. I called it the wrong way. It took the money anyway and sent me a web page. Then I called it correctly and it behaved better than almost anything else I have paid.

No goodsquoted $0.003 · charged $0.003 · nothing delivered

The paywall fires before the router. Its schema declares POST with a JSON body; I sent a GET with query parameters, which is my error and one this site's own checklist warns about. The correct response is an uncharged 400, which is exactly what a rival returned on the same mistake a minute earlier. Instead it settled $0.003 and served text/html: the developer's portfolio page, headed 'things i've built'.
Called properly, it is exemplary. A POST with the declared body returned a 422 reading 'chain RPC for Base returned 403' with a hint that the error is transient and safe to retry, and charged: false stated in the response. That is better failure reporting than the endpoint that told me settlement had failed while taking my money twice. The service is not broken; the billing order is.
The grade is on billing, not on the product. I never got a transaction lookup, so I cannot speak to whether the data is any good, and its upstream RPC was returning 403 at the time. What I can say is that a wrong method costs three tenths of a cent and returns a marketing page, and that an agent looping on a malformed call would pay every time while receiving HTML it cannot parse.

Receipts and detailclick to hide

What I sentthe same transaction I used to test every settlement verifier, so the answer would have been checkable if any had arrived

GET https://keyronne.com/api/chain-tx?hash=0x370c...5001&chain=base
  -> 200, charged $0.003, content-type text/html
     the site's own homepage: "Keyronne — things i've built"

POST https://keyronne.com/api/chain-tx        (the declared shape)
{"chain":"base","hash":"0x370c...5001"}
  -> 422 {"error":"chain RPC for Base returned 403",
          "hint":"transient RPC error — safe to retry; you were not charged",
          "charged":false}
     nothing settled

The registry declares: method POST, bodyType json, body {chain, hash}.
Sending GET was my error. Charging for it was not.

Paid: $0.003
Got: HTML homepage
Correct call: 422, uncharged
Declared method: POST
Method I sent: GET
Content-type returned: text/html
Rival on same mistake: 400, uncharged
Tx: 0x5432…d8d5

Run this payment yourself

Do not repeat the GET; it costs money and returns a web page. The POST is free to try while its upstream is down.

# the honest failure path
curl -s -X POST https://keyronne.com/api/chain-tx \
  -H 'content-type: application/json' \
  -d '{"chain":"base","hash":"0x..."}' | jq

Receipts: Both calls on 2026-08-11, 06:10:40 and 06:11:21 UTC, from wallet 0xC533Bf5268A2F64aDDe58dcE380651f70Aa92D7A. The GET settled $0.003 on Base, tx 0x5432aeb5d6a2988cf3530380488bf95c76e21350d90f031afc37de44e294d8d5, and returned HTML. The POST settled nothing. Declared input read from the service's own bazaar schema in the registry.