Discover / x402.shortforge.dev

Endpoint Liveness Probe

□ No challenge detected

A measured verdict on whether an endpoint is actually alive. Every reason carries the source it was read from. Sold per call over x402 on Base: probe ($0.01/call, GET /x402/probe); report ($0.50/call, GET /x402/report); batch ($0.10/call, POST /x402/batch).

Challenge detected
5 of the last 9 checks
Median response
190 ms
Last checked
16 Oct, 21:19 UTC
In our index since
26 Sept 2026

Endpoint

curl -i https://x402.shortforge.dev
# 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/x402.shortforge.dev

Recent checks

3 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.16 Oct 2026
All 9 checks
When (UTC)ResultHTTPResponse
16 Oct, 21:19 UTCNo challenge detected53067ms
15 Oct, 14:11 UTCNo challenge detected530117ms
14 Oct, 08:45 UTCNo challenge detected530149ms
12 Oct, 00:34 UTCChallenge detected402297ms
10 Oct, 10:04 UTCChallenge detected402153ms
9 Oct, 06:42 UTCChallenge detected402190ms
8 Oct, 03:32 UTCChallenge detected402160ms
7 Oct, 00:45 UTCChallenge detected402205ms
3 Oct, 05:05 UTCNo challenge detected502136ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 16 Oct, 21:19 UTC, we detected no payment challenge.

What payment terms does Endpoint Liveness Probe advertise?

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

Where is Endpoint Liveness Probe listed?

In x402 Bazaar and x402-list.com. Superstables first indexed it on 26 Sept 2026.

Something wrong on this page? Tell us.