Discover / crypto-threat-signals-api.onrender.com

crypto-threat-signals-api.onrender.com

■ Challenge detected

Up to 20 recent crypto risk reports for triage and review, with sources, validation status and cached PG1 checks when available. Reports may lack independent confirmation. USDC 0.01 per snapshot; not trade instructions or a safety guarantee.

x402
Base
USDC

Challenge detected: 1 of the last check
Median response: 168 ms
Last checked: 4 Oct, 05:05 UTC
In our index since: 4 Oct 2026

Endpoint

curl -i https://crypto-threat-signals-api.onrender.com/x402/signals
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/crypto-threat-signals-api.onrender.com

Recent checks

4 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.4 Oct 2026

All 1 checks

When (UTC)	Result	HTTP	Response
4 Oct, 05:05 UTC	Challenge detected	402	168ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 4 Oct, 05:05 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does crypto-threat-signals-api.onrender.com advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is crypto-threat-signals-api.onrender.com listed?

In x402 Bazaar. Superstables first indexed it on 4 Oct 2026.

Something wrong on this page? Tell us.