x402 List Submit a serviceSubmit
Menu

jsonguard

offline

payment-ready 2026-10-08, probe currently failing

Repair malformed JSON and validate against a JSON Schema.

Part of the Leeworks operator hub

jsonguard.leeworks.dev ↗

Call it x402 v2

x402 v2

Base URL
https://jsonguard.leeworks.dev
Payment
x402 v2, header channel
$ curl -i -X POST 'https://jsonguard.leeworks.dev/v1/validate'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.

Endpoints 1 paid route on jsonguard.leeworks.dev

POST/v1/validateBase$0.01since 07-25

Prices as captured in the 402 response: $0.01.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/v1/validateNo description$0.01BaseUSDCheadersince 07-25

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor.

134 lines, scroll inside

{
  "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
}

Can I trust it score from our own monitoring

score from our own monitoring

78/100 Solid

#13 of 17 in Compute. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
95% uptime 30d
Compliance
A 14/14 checks pass, stale (probe failing)
Price
$0.01 p63 in Compute
Risk
clean no risk flag
Traction
---
14/14 compliance checks
  • 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

402 terms unchanged since 2026-07-25. Last up 2026-10-08.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status offline, 95% uptime 30d, 1346ms response p95, x402 compliance 14 of 14, $0.01 price against the category. 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.

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.

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 17 listings, this one among them: the same 17 the position above is counted against. When the two differ, the field is the wider one, 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.

All measured facts

What it does

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.

jsonguard is a listed x402 Compute API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-09-24 to 2026-10-23 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Compute

uptime · latest daily rollup
0%
uptime 7d
0%
uptime 30d
95%
uptime 90d
98.9%
response p95
1346ms
avg response
1230ms
total checks
1,472

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min)
$0.01
category percentile (min)
p63 in Compute
endpoints / prices
1 / 1
model
flat
stability
100%

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.

This service shares a payout address and its probe has been failing, so its on-chain volume is suppressed until it responds again. Settlements on a shared address while a member is down are not attributed to it.

member since
2026-07-25
Recent checks
Latest 18 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Offline4045694ms0
Offline4041807ms0
Offline4041915ms0
Offline4041424ms0
Offline4041711ms0
Offline4041757ms0
Offline4041988ms0
Offline4042599ms0
Offline4041264ms0
Offline4041371ms0
Offline4041109ms0
Offline4042014ms0
Offline4041444ms0
Offline4041993ms0
Offline4044593ms0
Offline4042558ms0
Offline4041861ms0
Offline4041360ms0

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume

This service shares a payout address and its probe has been failing, so its on-chain volume is suppressed until it responds again. Settlements on a shared address while a member is down are not attributed to it.

Uptime 15 of 29 completed days below 100%
uptime below 100%, to scale uptime 0%
Uptime
15 of 29 completed days below 100%

This service shares a payout address and its probe has been failing, so its on-chain volume is suppressed until it responds again. Settlements on a shared address while a member is down are not attributed to it.

More charts
Response time daily average, ms min 919ms, avg 1237ms, max 1449ms

09-24 to 10-23* UTC

Scores over time

x402 compliance low 14/14, high 14/14

09-24 to 10-23* UTC

Price percentile in Compute own low to high; exact values below

09-24 to 10-23* UTC

Site signals present (of 6) own low to high; exact values below

09-24 to 10-23* UTC

Scores: one day per column, 09-24 to 10-23*, on the columns of Response time. Uptime held below 100% on some days in this window, including any partial day. Daily readings remain in the Uptime strip and Values. The checklist grew from 11 to 14 checks on 2026-07-28, before this window. Pillar lines use their own low and high. Exact dated readings are available in each readout and in Values.

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.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-09-24 to 2026-10-23: uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayUptimeResponseCompliancePrice percentileSite signals
2026-09-24100%1379.19ms14/14p643/6
2026-09-25100%1445.68ms14/14p643/6
2026-09-26100%1370.88ms14/14p643/6
2026-09-27100%1393.45ms14/14p643/6
2026-09-28100%1422.18ms14/14p643/6
2026-09-29100%1448.12ms14/14p643/6
2026-09-30100%1448.66ms14/14p643/6
2026-10-01100%1279.23ms14/14p643/6
2026-10-02100%1314.97ms14/14p643/6
2026-10-03100%1182.89ms14/14p643/6
2026-10-04100%977.36ms14/14p643/6
2026-10-05100%946.18ms14/14p643/6
2026-10-06100%918.97ms14/14p643/6
2026-10-07100%926.64ms14/14p643/6
2026-10-0886.84%1106.06ms14/14p643/6
2026-10-090%no data14/14p641/6
2026-10-100%no data14/14p641/6
2026-10-110%no data14/14p641/6
2026-10-120%no data14/14p641/6
2026-10-130%no data14/14p641/6
2026-10-140%no data14/14p631/6
2026-10-150%no data14/14p631/6
2026-10-160%no data14/14p631/6
2026-10-170%no data14/14p631/6
2026-10-180%no data14/14p631/6
2026-10-190%no data14/14p631/6
2026-10-200%no data14/14p631/6
2026-10-210%no data14/14p631/6
2026-10-220%no data14/14p631/6
2026-10-23*0%no data14/14p631/6

Alternatives in Compute

QuickNode solid 89/100 100% up 30d $0 30d
agent-exec solid 88/100 99.9% up 30d $0 30d
Coprocesseur déterministe solid 88/100 100% up 30d $0.002 30d
Cloud World Model solid 86/100 100% up 30d $0.04 30d
Shehriyars API solid 86/100 100% up 30d $0.002 30d

5 of 16 other ranked services in Compute, ordered by the same measured score.

see the whole category

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)
Embed a badge

HTML

<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>

Markdown

[![jsonguard on x402-list](https://x402-list.com/badge/jsonguard.svg)](https://x402-list.com/services/jsonguard?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<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>
Delisting

To request delisting, email info@x402-list.com with the service name, slug, or URL. Removal is free and does not require proof of ownership. Contact.