payment-ready until 2026-10-06
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.
Part of the Leeworks operator hub
Pay from $0.01 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.
measured since 2026-07-21 (start of our harvest window) · $0.19 all-time · settled via payAI
VERDICT
ranking generation 3solid 79/100 #10 of 16 in Compute by measured score
What the score read on this service: status online, 99.9% uptime 30d, 2333ms response p95, x402 compliance 14 of 14, $0.01 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
It is a score inside Compute, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 16 listings, this one among them. That set is wider than the 16 the position above is counted against, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
ALTERNATIVES IN COMPUTE
Other Compute services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).
| SERVICE | BAND | SCORE | UPTIME 30D | VOL 30D |
|---|---|---|---|---|
| QuickNode | solid | 89 | 100% | $0 |
| Cloud World Model | solid | 88 | 99.9% | $0.92 |
| Coprocesseur déterministe | solid | 87 | 100% | $0.002 |
| agent-exec | solid | 86 | 99.9% | $0 |
| Shehriyars API | solid | 86 | 100% | $0.002 |
ASSESSMENT
updated 2h agoThe parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.
reliability 99.9%
- uptime · latest daily rollup
- 100%
- uptime 7d
- 100%
- uptime 30d
- 99.9%
- uptime 90d
- 99.8%
- response p95
- 2333ms
- avg response
- 1157ms
- total checks
- 2,696
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
compliance A (14/14)
14 of 14 x402 conformance checks pass. Full checklist below.
price $0.01 (p64 in Compute)
- price (min)
- $0.01
- category percentile (min)
- p64 in Compute
- endpoints / prices
- 1 / 1
- model
- flat
- stability
- 100%
risk clean
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
- domain age
- -
- registrar
- -
- hosting
- custom
- domain created
- ---
Identity facts, not a risk score.
traction $0.0016666667 30d · 1 buyers · top buyer 100% (address, not entity)
- volume 30d
- $0.0016666667
- buyers 30d
- 1
- settlements 30d
- 1
- measured since
- 2026-07-21 (start of our harvest window)
- last settlement
- 2026-09-01
- top buyer share
- 100% of 30d volume (address, not entity)
- trend 7d vs 30d
- 0.00x the 30d daily rate
- networks
- eip155:8453
- volume all-time
- $0.19
- settlements all-time
- 24
- median settlement 30d
- $0.01
- max settlement 30d
- $0.01
- settled via
- payAI ($0.01, 1 tx)
Attributed pro-quota: this payout address is shared, so volume is the operator-level figure divided by the services sharing it, while buyer and transaction counts stay whole. A declared convention, not an individually observed measure, and still a conservative undercount.
Currently sharing this payout address with agentmail, chainfeed, chainkit, difftool, x402 Agent-Commerce Starter + Platform Map.
Top buyer share is part of the ranking score: a higher share lowers the traction part of the score, by up to half when one address holds all 30d volume.
WHAT IT DOES
ai-derivedNo AI synthesis has been produced for this service yet.
ENDPOINTS
| METHOD | PATH | DESCRIPTION | PRICE | NETWORK | ASSET | 402 CHANNEL |
|---|---|---|---|---|---|---|
| POST | /v1/validate | $0.01 | Base | USDC | header |
REQUEST / RESPONSE EXAMPLE
An unpaid request to POST /v1/validate returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
curl -i -X POST 'https://jsonguard.leeworks.dev/v1/validate'
// 402 response (captured by monitor) · 1 payload · click to expand
[
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xa8B061d96F69426f11bcC807BfA00f0AF79541a7",
"amount": "10000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"resource": {
"url": "http://jsonguard.leeworks.dev/v1/validate",
"mimeType": "application/json",
"description": "Repair malformed JSON and validate against a JSON Schema"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"data": "{name:'ada', tags:['x',]}",
"schema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
}
}
}
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"valid": true,
"errors": null,
"parsed": {
"name": "ada"
},
"repaired": "{\"name\":\"ada\"}",
"repairError": null
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"data"
],
"properties": {
"data": {
"type": [
"string",
"object",
"array"
],
"description": "Malformed JSON string (repaired) or a parsed value"
},
"schema": {
"type": "object",
"description": "Optional JSON Schema to validate against"
}
}
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
},
"x402Version": 2
}
] OVER TIME
All charts use the 7d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/jsonguard/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.
checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression
Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.
Shared payout address (5 other services). These bars are the full shared address (operator-level), so do not sum them across the services that share it. Where a per-service figure is attributed, the assessment block and the ranking, it is the address total divided pro-quota by the 6 services sharing it: a declared convention, not an individually observed measure.
Shared payout address (5 other services). These bars are the full shared address (operator-level), so do not sum them across the services that share it. Per-service buyer and transaction counts are shown whole (integers), not divided; only volume is attributed pro-quota. A declared convention, not an individually observed measure.
COMPLIANCE
14/14 checks pass · grade Alast 402 captured 2026-07-25 · last up 2026-09-29
- 402 payload captured
- accepts[] array present
- payTo address recoverable
- payTo at accepts[0].payTo (conformant shape)
- payTo is a valid on-chain address
- atomic price declared
- atomic price in a sane range
- asset (token) address declared
- network resolves to CAIP-2
- payment scheme declared
- served over HTTPS
- declares the current x402 version (2)
- EIP-712 domain parameters present on every EVM entry
- x402 v2 envelope delivered in the payment-required header
SITE PILLARS
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
recent checks (18) live · click to expand
EMBED THIS BADGE
<a href="https://x402-list.com/services/jsonguard?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/jsonguard.svg" alt="jsonguard listed on x402-list" height="28"> </a>
[](https://x402-list.com/services/jsonguard?utm_source=badge&utm_medium=referral&utm_campaign=embed)
<a href="https://x402-list.com/services/jsonguard?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/jsonguard.svg?data=uptime" alt="jsonguard uptime on x402-list" height="28"> </a>