Menu

Two Listings Held, Not Rejected — a Per-Path Cloudflare Challenge on an x402 Endpoint
📰

Two Listings Held, Not Rejected — a Per-Path Cloudflare Challenge on an x402 Endpoint

DEV Community: api·minia2a·3 days ago
#rkcsIo8z
#devtoapi#devto#dev#challenge#path
Reading 0:00
15s threshold

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.

Two Listings Held, Not Rejected

2026-10-23 · review queue

A batch of 22 service submissions arrived at once. We reviewed them serially, probed each published path once, and ended with 19 approved, 1 rejected, 2 held . The interesting part is the two we did not decide.

What the queue looked like

Outcome Count Reason

approved 19 unpaid POST → 402 with accepts

rejected 1 description was the placeholder n/a ; the URL was a share-link page, not an API

held 2 ⚠ no verdict — see below

Sixteen of the approvals point at one host. Two more paths on that same host did not answer 402.

Same host, different answer, different path

POST /api/v1/util/slugify -> 402 accepts[1] eip155:8453 POST /api/v1/market/price -> 402 accepts[1] eip155:8453 ...…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.