78trust / 100

Schema Validate

by NetIntel in Documents & files

x402 APIPassing, checked 37 min ago

Validate data against a supplied schema — checks required fields, nested objects, arrays, enums, string formats, numeric ranges, lengths, and additional-property rules deterministically, with optional type coercion and repair, returning precise errors with JSON paths so agents can verify structured data before acting on it.

POST
https://netintel.dev/schema/validate
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
314 ms
405 ms slowest 5%
Last check
Passed
37 min 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://netintel.dev/schema/validate

Each call costs $0.02 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://netintel.dev/schema/validate
content-type: application/json

{
  "data": {
    "age": "42",
    "name": "Acme"
  },
  "schema": {
    "age": "number",
    "email": "email",
    "name": "string"
  }
}

Parameters

ParameterTypeRequiredDescription
allow_llmbooleanNoDefault true. Gates the LLM repair fallback only — validation itself is always deterministic.
coercebooleanNoDefault false. Coerce values to the declared types where lossless ("5" → 5, "yes" → true).
dataobject or array or stringYesThe data to validate: an object, an array, or a JSON string (malformed strings are repaired first). Max 64KB.
repairbooleanNoDefault false. When invalid, also return a repaired copy of the data plus is_repaired_valid. Deterministic first (coercion, declared defaults, enum casing, strict extra-key removal).
schemaobjectYesJSON Schema ({"type":"object","properties":{...},"required":[...]}) or a simplified field→type map ({"age":"number","email":"email","tags":"string[]","bio":"string?"}). In the map form a field is required unless suffixed with '?'. Formats: email, url, date, date-time, uuid, ipv4, ipv6, hostname.

Example response

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

Example response, 31 lines
{
  "coerced": false,
  "error_count": 2,
  "errors": [
    {
      "expected": "required",
      "message": "required field is missing",
      "path": "$.email",
      "received": "undefined"
    },
    {
      "expected": "number",
      "message": "expected number, received string",
      "path": "$.age",
      "received": "string"
    }
  ],
  "findings": [
    {
      "deduction": 0,
      "detail": "Data does not satisfy the schema (2 errors)",
      "rule": "data_invalid"
    }
  ],
  "grade": "A",
  "is_repaired_valid": null,
  "repaired": null,
  "score": 100,
  "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.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://netintel.dev/schema/validate' \
  -H 'content-type: application/json' \
  --data-raw '{"data":{"age":"42","name":"Acme"},"schema":{"age":"number","email":"email","name":"string"}}'

# 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://netintel.dev/schema/validate' \
  -H 'content-type: application/json' \
  --data-raw '{"data":{"age":"42","name":"Acme"},"schema":{"age":"number","email":"email","name":"string"}}' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fnetintel.dev%2Fschema%2Fvalidate&method=POST
const res = await pay("https://netintel.dev/schema/validate", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "data": {
      "age": "42",
      "name": "Acme"
    },
    "schema": {
      "age": "number",
      "email": "email",
      "name": "string"
    }
  }),
});
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://netintel.dev/schema/validate",
        json={
            "data": {
                "age": "42",
                "name": "Acme",
            },
            "schema": {
                "age": "number",
                "email": "email",
                "name": "string",
            },
        },
    )
    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
37 min agoPassed402328 ms$0.02
5 h agoPassed402341 ms$0.02
10 h agoPassed402326 ms$0.02
14 h agoPassed402314 ms$0.02
18 h agoPassed402251 ms$0.02
Show 10 older checks
22 h agoPassed402346 ms$0.02
27 h agoPassed402256 ms$0.02
31 h agoPassed402329 ms$0.02
35 h agoPassed402400 ms$0.02
40 h agoPassed402258 ms$0.02
44 h agoPassed402333 ms$0.02
2 days agoPassed402367 ms$0.02
2 days agoPassed402253 ms$0.02
2 days agoPassed402315 ms$0.02
3 days agoPassed402178 ms$0.02