DEV Community

minia2a
minia2a

Posted on Edited on Originally published at minia2a.uk

The probe wanted HTTP 402. Our MCP door answers 200

This content reflects minia2a as of its publication date and is kept for the record. Current model: x402 pay-per-call in USDC on Base only, 5 free trial calls per signed wallet, no credits and no top-up rail.

The probe wanted HTTP 402. Our MCP door answers 200.

November 2026

A directory can index your endpoint and still never verify it. Ours sat
unverified with the reason recorded in the probe result: not_payment_gated,
next to http_status: {"get": 200, "post": 400}. Neither of those is 402. The
prober was reading the HTTP status line, and on that path we never send one.

Two doors, one challenge, two statuses

Both of these are the same endpoint refusing the same unpaid call. Measured on
16 November 2026:

Unpaid request Status Bytes Where the 402 is
GET /x402/weather?city=London 402 2,957 top level: error: "Payment required" + accepts[]
POST /mcp tools/call 200 3,065 in the envelope: error.code: 402

The MCP refusal, trimmed:

{"jsonrpc":"2.0","id":7,
 "error":{"code":402,
          "message":"free trial is wallet-based or disabled — pay via x402",
          "data":{"accepts":[{"amount":"10000","asset":"0x833589fC…2913",
                              "network":"eip155:8453",
                              "payTo":"0xAb62452b…A7Bf","scheme":"exact"}],
                  "extensions":{"bazaar":{…}},"error":"Payment required"}}}
Enter fullscreen mode Exit fullscreen mode

The whole payable document is there — accepts, the bazaar extension, the resource
description — nested one level deeper, under error.data. A client that parses the
JSON-RPC envelope reads the same challenge a client of the HTTP door reads. A client that reads
response.status sees success.

That is a transport decision, not a bug. MCP clients parse one JSON-RPC
envelope per response; the refusal travels inside it. We have measured three different refusing
shapes across x402 MCP servers and none of them is universal, so this is not a standards claim —
it is what our door does, and what a status-reading probe therefore cannot see.

Why we did not change the door

The cheap fix was to return HTTP 402 on the MCP path for a few seconds of prober traffic.
We did not, for one reason: it changes the contract for every MCP client in order to satisfy one
reader's assumption. An MCP client that branches on response.ok would take a 402 as a
transport failure rather than a payment request; the JSON-RPC envelope it expects would be
unreachable behind a status code. A probe is a sample of clients, not all of them.

The directory's own check does open an MCP session for /mcp paths, so the shape
was anticipated — the verdict still required the HTTP status. Anticipating a transport and
accepting it are different things, and we would rather be absent from a list than
misrepresent the door we serve.

What we listed instead

https://minia2a.uk/x402/weather — an ordinary HTTP 402 door, $0.01 per call. The
listing fee was $0.25 USDC on Base, paid over x402 on the same POST:

tx    0xcaad4977c1e636ee82c3f593d2b9591ed4b82f22216a84e16a95a8f219d3e6dc
block 58012630   transfer 0x3d090 = 250000 atomic USDC
Enter fullscreen mode Exit fullscreen mode

What the $0.25 bought

Time (UTC) Event
01:35 listing created, status unverified
01:36:30 first probe passed — GET, probes_passed 1 / probe_count 1
02:12:31 status flipped to verified at 4/4 probes, consecutive_failures 0, score 1
02:42:43 latest probe passed; interval settled at 1,800 s

And the part the badge does not say: evidence_tier: "probe_only", with their own
note, “Passing checks, but a short history so far. Treat as provisional.”
paid_verified is still false, distinct_payers is 0, and
latest_purchase_at is null. The fee includes one real purchase of the endpoint by
their buyer — within 48 hours of first verifying, if the endpoint quotes $0.05 or less — and it
has not run yet. A passing probe is a statement about the refusal, not about delivery.

The two paid tiers are not the same tier

This is the part I would have got wrong by reading the price list quickly:

Tier Price What it buys
new listing $0.25 the listing, plus one real purchase included
verify-now?plan=recheck $0.25 + endpoint price one more real purchase, within 24 h
verify-now?plan=monthly $1 + 4 × endpoint price four purchases over 30 days

For a $0.01 endpoint, recheck is $0.26 as a separate charge — the included purchase in the
listing fee is not a down payment on it. If you budget “listing + verification = $0.25” you are
short by a whole tier.

Verified is a filter, not a badge

Their discovery endpoint sorts verified listings first, then by score, then by price. A search
for weather returned fifteen results, all verified; ours sat third, behind two cheaper
listings. So $0.25 did not buy a ranking — it bought admission to the set that gets ranked. That
distinction matters when you decide whether to pay: unverified is invisible at the top of the list
regardless of how good the endpoint is, and verified is table stakes, not a win.

If you are about to list an endpoint

  1. Run the free check first. POST /v1/check returns what the prober would do to your URL without creating or charging anything (30 per hour per IP). It answers the only question worth asking before paying: would this verify?
  2. Know what your unpaid refusal looks like on the wire. If it is a JSON-RPC error inside HTTP 200, every prober that reads the status line will call it not_payment_gated. List an HTTP endpoint instead of bending the transport.
  3. Read the fee description, not the fee. “$0.25 per listing” and “$0.25 plus one included purchase” are different products.
  4. Treat a probe pass as provisional. The listing says so itself; believe it until a paid purchase shows up in the history.

minia2a is a pay-per-call market for x402 endpoints, priced in USDC on Base
with five free trial calls per signed wallet. Every number above was read from the live endpoints
and the directory's own API on 16 November 2026, not from a summary.

Update, 17 November 2026 — the listing is verified

Two days after the fee, the listing reads what we hoped it would:

GET https://nohumans.directory/v1/listings/5288884d-698

status                 verified
verified_via           GET
probes_passed          57 / 57      consecutive_failures 0
score                  1
evidence_tier          paid_verified
evidence_note          "We paid this endpoint real USDC and confirmed
                        settlement on-chain; the response was inspected."
Enter fullscreen mode Exit fullscreen mode

That last field is the part a listing fee actually buys: a third party paying
our endpoint with its own money, checking the settlement on chain, and reading
the response. Their paid call is in our ledger too, not just in their claim:

credit_ledger      id 6170 | spend | 1 | x402-weather
                   agent 0x54E163e9B8eDDa194D83F46AdD921bfA5fc5f4E0
                   ref   facilitator:0x96dbea55…9291c3
                   at    2026-11-16 08:30:56
delivery_outcomes  id 8380 | x402-weather | paid | ok
                   ua    nohumans-scout/1.0 (+https://nohumans.directory)
                   at    2026-11-16 08:30:56
Enter fullscreen mode Exit fullscreen mode

One spend row, one delivery row, same second, delivery ok.

What did not change: the /mcp entry is still
unverified by this directory's rule — their prober reads the HTTP status, and an
unpaid MCP call is HTTP 200 carrying a JSON-RPC error code 402. Verification will
attach to the HTTP /x402/<id> path, which is what the listing
buys and what the prober can read.

One detail worth carrying into any discovery budget: this directory sorts
verified → score → price, so an unverified endpoint is not merely behind
a badge — it is behind the sort key. A $0.01 endpoint that nobody has paid for can
sit below a verified demo that costs nothing at all.


Originally published at minia2a.uk.

Top comments (0)