ToolVet
77trust / 100

Json Schema Validate

by JSON Schema Validator in Markets & finance

x402 APIPassing, checked 5 h ago

JSON Schema validation — validate JSON records, invoices and payloads against the bounded Draft 2020-12 Atlas profile; return valid status and deterministic JSON Pointer errors. This validator subset supports exact numbers and local references with Go RE2 patterns; unsupported schemas are rejected and remote schemas are never loaded.

POST
https://data-tools.use.x402atlas.com/json-schema-validate
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
455 ms
522 ms slowest 5%
Last check
Passed
5 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://data-tools.use.x402atlas.com/json-schema-validate

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

POST https://data-tools.use.x402atlas.com/json-schema-validate
content-type: application/json

{
  "instance": {
    "bar": {},
    "foo": 1
  },
  "profile": "draft2020-12-atlas-profile-v1",
  "schema": {
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "bar": {
        "type": "string"
      },
      "foo": {
        "type": "integer"
      }
    }
  }
}

Parameters

ParameterTypeRequiredDescription
instanceobject or array or string or number or boolean or nullYesInstance to validate, <=512 KiB; unique decoded keys, valid Unicode, depth <=64, finite JSON numeric tokens <=1024 bytes and exponent magnitude <=4096
profilestringNoExplicit supported Draft 2020-12 subset; omitted value uses this profile Default: "draft2020-12-atlas-profile-v1".
schemaobject or booleanYesLocal Draft 2020-12 profile schema, <=512 KiB; all supplied positions are statically checked; supported keywords and regex work limits documented in route details

Example response

The provider's example. We can't check it without paying.

{
  "algorithm_version": "draft2020-12-atlas-profile-v1",
  "errors": [
    {
      "instance_pointer": "/bar",
      "keyword": "type",
      "message": "value does not satisfy type constraint",
      "schema_pointer": "/properties/bar/type"
    }
  ],
  "input": {
    "instance_node_count": 3,
    "profile": "draft2020-12-atlas-profile-v1",
    "schema_node_count": 7
  },
  "operation": "json-schema-validate",
  "valid": false,
  "warnings": []
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://data-tools.use.x402atlas.com/json-schema-validate' \
  -H 'content-type: application/json' \
  --data-raw '{"instance":{"bar":{},"foo":1},"profile":"draft2020-12-atlas-profile-v1","schema":{"$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"bar":{"type":"string"},"foo":{"type":"integer"}}}}'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://data-tools.use.x402atlas.com/json-schema-validate' \
  -H 'content-type: application/json' \
  --data-raw '{"instance":{"bar":{},"foo":1},"profile":"draft2020-12-atlas-profile-v1","schema":{"$schema":"https://json-schema.org/draft/2020-12/schema","properties":{"bar":{"type":"string"},"foo":{"type":"integer"}}}}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fdata-tools.use.x402atlas.com%2Fjson-schema-validate&method=POST
const res = await pay("https://data-tools.use.x402atlas.com/json-schema-validate", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "instance": {
      "bar": {},
      "foo": 1
    },
    "profile": "draft2020-12-atlas-profile-v1",
    "schema": {
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "bar": {
          "type": "string"
        },
        "foo": {
          "type": "integer"
        }
      }
    }
  }),
});
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://data-tools.use.x402atlas.com/json-schema-validate",
        json={
            "instance": {
                "bar": {},
                "foo": 1,
            },
            "profile": "draft2020-12-atlas-profile-v1",
            "schema": {
                "$schema": "https://json-schema.org/draft/2020-12/schema",
                "properties": {
                    "bar": {
                        "type": "string",
                    },
                    "foo": {
                        "type": "integer",
                    },
                },
            },
        },
    )
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
5 h agoPassed402452 ms$0.01
9 h agoPassed402515 ms$0.01
14 h agoPassed402466 ms$0.01
18 h agoPassed402435 ms$0.01
23 h agoPassed402479 ms$0.01
Show 10 older checks
27 h agoPassed402520 ms$0.01
31 h agoPassed402454 ms$0.01
35 h agoPassed402522 ms$0.01
40 h agoPassed402469 ms$0.01
44 h agoPassed402508 ms$0.01
2 days agoPassed402421 ms$0.01
2 days agoPassed402420 ms$0.01
2 days agoPassed402414 ms$0.01
3 days agoPassed402455 ms$0.01
3 days agoPassed402474 ms$0.01