Discover / api.pulsewatch.us

api.pulsewatch.us

■ Challenge detected

PulseWatch Status API: Current outage status for a vendor (PulseWatch). Current status, active-incident summary, last-checked time and source URL for one vendor, read live from PulseWatch. Includes data_source, checked_at and freshness fields. Unknown vendors return 404 and are not charged.

x402
Base
USDC

Listed price: $0.01
Challenge detected: 1 of the last check
Median response: 213 ms
Last checked: 10 Oct, 12:22 UTC
In our index since: 10 Oct 2026

Endpoint

curl -i https://api.pulsewatch.us/v1/status
# 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/api.pulsewatch.us

Recent checks

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

All 1 checks

When (UTC)	Result	HTTP	Response
10 Oct, 12:22 UTC	Challenge detected	402	213ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 10 Oct, 12:22 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 price is recorded for api.pulsewatch.us?

Its listed price is $0.01.

What payment terms does api.pulsewatch.us 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 api.pulsewatch.us listed?

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

Something wrong on this page? Tell us.