payment-ready until 2026-08-20
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.
Pay from $0.01 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.
first settlement 2026-07-21 · $0.17 all-time · settled via payAI, coinbase
ASSESSMENT
updated 1h agoEvidence-backed signals, not a single score. Click any chip for the proof. Measured values stay read-only; unknown is honest.
reliability 99.6%
- uptime 24h
- 100%
- uptime 7d
- 100%
- uptime 30d
- 99.6%
- uptime 90d
- 99.6%
- response p95
- 1580ms
- avg response
- 1009ms
- total checks
- 1,712
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 (p67 in Compute)
- price (min)
- $0.01
- category percentile (min)
- p67 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.1683333333 30d · 3 buyers
- volume 30d
- $0.1683333333
- buyers 30d
- 3
- settlements 30d
- 17
- first settlement
- 2026-07-21
- last settlement
- 2026-08-06
- top buyer share
- 74% of 30d volume
- trend 7d vs 30d
- 0.51x the 30d daily rate
- networks
- eip155:8453
- volume all-time
- $0.17
- settlements all-time
- 17
- median settlement 30d
- $0.10
- max settlement 30d
- $0.10
- settled via
- payAI ($0.66, 9 tx), coinbase ($0.35, 8 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 a concentration signal, not part of the ranking score.
WHAT IT DOES
ai-derivedRepairs malformed JSON and validates it against a JSON Schema
- category
- -validation
- in
- body
AI-generated summary. The measured data is never altered by it.
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 90d 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-08-13
- 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>