Discover / chrono.schemasure.com

ChronoSure

□ No challenge detected

Resolve a local time to an exact UTC instant with explicit DST ambiguity handling, business-day arithmetic, public-holiday status, and working-hour overlap across timezones. Detects ambiguous and nonexistent local times instead of silently shifting them. Declares its IANA tzdb release and per-jurisdiction holiday provenance.

Listed price
$0.02
Challenge detected
0 of the last check
Last checked
14 Oct, 17:47 UTC
In our index since
14 Oct 2026

Endpoint

curl -i https://chrono.schemasure.com/v1/business-time
# 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/chrono.schemasure.com

Recent checks

14 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.14 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
14 Oct, 17:47 UTCNo challenge detected404770ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 14 Oct, 17:47 UTC, we detected no payment challenge.

What price is recorded for ChronoSure?

Its listed price is $0.02.

What payment terms does ChronoSure 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 ChronoSure listed?

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

Something wrong on this page? Tell us.