Discover / jsonguard.leeworks.dev

jsonguard

□ No challenge detected

Repair malformed JSON and validate against a JSON Schema. POST malformed JSON (and an optional schema); returns repaired text, the parsed value, and validation errors. 0.01 USDC on Base per call via x402, no account.

x402
Base
USDC
Compute

Challenge detected: 0 of the last 3 checks
Last checked: 16 Oct, 21:19 UTC
In our index since: 14 Oct 2026

Endpoint

curl -i https://jsonguard.leeworks.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/jsonguard.leeworks.dev

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

All 3 checks

When (UTC)	Result	HTTP	Response
16 Oct, 21:19 UTC	No challenge detected	404	165ms
15 Oct, 14:11 UTC	No challenge detected	404	335ms
14 Oct, 05:00 UTC	No challenge detected	404	91ms

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 jsonguard advertise?

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

Where is jsonguard listed?

In x402-list.com. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.