x402 operator - independently measured by Market402. Status: probed, not yet verified
Capability tags (auto-derived from listed descriptions): geo-ip. Machine-readable: /badge/dns-intel-api-production.up.railway.app (live JSON) | /op/dns-intel-api-production.up.railway.app.json (score history + trend) | /operators.json. Updated 2026-09-16T03:11 UTC, refreshed by weekly full-census probes.
trend: stable | volatility: low | 5 weekly observations (rules: Score history v1.5; derived verdicts need 4+ weeks). Machine-readable: /op/dns-intel-api-production.up.railway.app.json
| week | score | badge |
|---|---|---|
| 2026-W38 | 100.0 | none |
| 2026-W37 | 100.0 | none |
| 2026-W36 | 100.0 | none |
| 2026-W35 | 100.0 | none |
| 2026-W34 | 100.0 | none |
| host | score | endpoints | verified |
|---|---|---|---|
| dns-intel-api-production.up.railway.app | 100.0 | 5 | 0 |
Verification is earned by measurement, never sold and never self-reported: pass spec + reliability checks over time and deliver on a real paid purchase (rules). Get probed via POST /submit; test your 402 for free at /selftest.
What the 402 Score measures: availability, latency, x402 spec compliance, price integrity and paid delivery - from real requests, by published rules. Scores are never self-reported and never sold.
From the operator (Mart402) - checked the seller? The other half of due diligence is verifying what it sends you (receipts, invoices, documents): the purchase-due-diligence workflow. This is a clearly labeled note from the index operator; it never affects scores or ranking.