Discover / sntl-router.vercel.app

SNTL DePIN Oracle (x402 Proxy)

□ No challenge detected

Pay-per-record access to the SNTL DePIN RF Telemetry & Yield Loss Oracle datalake. Proxies to the SNTL backend; payments settle to the SNTL treasury.

Challenge detected
0 of the last 2 checks
Last checked
8 Oct, 15:20 UTC
In our index since
7 Oct 2026

Endpoint

curl -i https://sntl-router.vercel.app/api/v2/anomalies
# 402 Payment Required: pay with a MPP client, then send the request again.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/sntl-router.vercel.app

Recent checks

7 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.8 Oct 2026
All 2 checks
When (UTC)ResultHTTPResponse
8 Oct, 15:20 UTCNo challenge detected404819ms
7 Oct, 03:20 UTCNo challenge detected404810ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 8 Oct, 15:20 UTC, we detected no payment challenge.

What payment terms does SNTL DePIN Oracle (x402 Proxy) advertise?

The listing advertises MPP, Tempo and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is SNTL DePIN Oracle (x402 Proxy) listed?

In mppscan. Superstables first indexed it on 7 Oct 2026.

Something wrong on this page? Tell us.