Validate JSON data against a JSON Schema (draft-07, Ajv)
Validate JSON data against a JSON Schema (draft-07, Ajv). Returns valid + detailed errors with instance paths.
by validate.yankii.fr · discovered, not yet claimed by its owner · updated 2026-10-09
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Validate JSON data against a JSON Schema (draft-07, Ajv). Returns valid + detailed errors with instance paths.
Tags: json · json-schema · validation · developer-tools · data-quality · bazaar
Call contract
- Method
- POST
- Input
- json
- Output
- json
- Last paid call
- 2026-10-09
{
"data": {
"age": 30,
"name": "John"
},
"schema": {
"properties": {
"age": {
"minimum": 0,
"type": "number"
},
"name": {
"type": "string"
}
},
"required": [
"name",
"age"
],
"type": "object"
}
}{
"errors": [],
"valid": true,
"validatedAt": "2026-10-03T10:00:00.000Z"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/36604.jsonfor the price and payment options. - Pay. Call
GET https://validate.yankii.fr/v1/validate. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.01 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 3 calls · 3 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.01 | 0x40661D56c2Bf416c5946A8b21098eaF8D33459A2 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x40661D56c2Bf416c5946A8b21098eaF8D33459A2",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"amountUsd": 0.01,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"properties": {
"errors": {
"items": {
"properties": {
"field": {
"type": "string"
},
"message": {
"type": "string"
},
"params": {
"type": "object"
}
},
"type": "object"
},
"type": "array"
},
"valid": {
"type": "boolean"
},
"validatedAt": {
"type": "string"
}
},
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {
"errors": [
{
"field": "string",
"message": "string",
"params": {}
}
],
"valid": true,
"validatedAt": "string"
},
"type": "string"
}Examples
curl "https://validate.yankii.fr/v1/validate"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://validate.yankii.fr/v1/validate");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://validate.yankii.fr/v1/validate")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- validate.yankii.fr
- Endpoint
- https://validate.yankii.fr/v1/validate
- Machine-readable
/resources/36604.json