Api — Opportunities Trending
Paid ($0.01 USDC via x402). Returns the top 20 active opportunity cards by score as TEASERS — { id, slug, title, category, score, signalCount, lastSeen } only. No evidence and no productAngle (buy GET /v1/opportunity for the full card). While the index is still warming and no active cards exist yet, you get a no-charge 503 corpus_warming (never an empty charged list) — poll the free GET /v1/categories to see when cards go live. Compute-first / settle-after — you are not charged on any error. Re…
Endpoint
https://api.demandex.dev/v1/opportunities/trending
Verification
We paid this endpoint real USDC and confirmed settlement on-chain; the response was inspected.
On-chain payments
Payment shape (25 most recent sampled): 25 x402-signed (EIP-3009 transferWithAuthorization, the exact scheme's on-chain signature) · 0 plain transfers (a wallet paying the ordinary way) · 0 other calldata (facilitator batch, smart wallet, or unrelated — not classified).
Peak day 2026-09-24: 29 payments. Last indexed day 2026-10-05: 8. Our own index of USDC Transfer events on Base to this payTo, updated every 10 minutes; window is today plus the 30 prior UTC days. Base USDC only — a seller settling elsewhere reads as quiet here. These figures belong to the address, which 11 listings declare — they are not this route's alone, and must not be summed across listings. Methodology.
last 30 probes, oldest → newest · 83% pass · re-probed on its probe tier's interval (next_check_by on the record) from nohumans infrastructure — never self-reported
Paid verification
✓ verified with real payment — 2026-09-01
$0.01 USDC paid on Base · tx ↗
response: valid JSON (no schema declared)
Real USDC was paid to this endpoint and the response inspected — not just a liveness check. One-time verification at the date shown, not continuous.
[](https://nohumans.directory/l/d41ebd34-d30)
Badge
[](https://nohumans.directory/l/d41ebd34-d30)
Machine interface
curl https://nohumans.directory/v1/listings/d41ebd34-d30
Own this service? Claim this listing to control its metadata — proof-of-control via your own endpoint, ~2 minutes. Works for submitted listings too, and recovers a lost token.