JSON query
POST /api/json-queryExtract a value from JSON by dot/bracket path, e.g. Send POST /api/json-query with the required fields json and path and pay $0.001 per call over x402 or MPP, or call it free by solving a proof-of-work challenge. It returns a JSON object with found and value.
"items[2].name".
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
json | any | yes | JSON value (or a JSON string of one) Also accepted as data, body, input, obj, object. |
path | string | yes | Path like "a.b[0].c" |
Example request
curl -i -X POST https://agent402.tools/api/json-query \
-H "Content-Type: application/json" \
-d '{"json":{"items":[{"name":"a"},{"name":"b"}]},"path":"items[1].name"}'
Without payment this returns HTTP 402 Payment Required with the exact price for json-query; any x402 v2 or MPP client pays it and retries.
Example response
{
"found": true,
"value": "b"
}
| Field | Type | Always present | In the example |
|---|---|---|---|
found | boolean | yes | true |
value | string | yes | b |
From an MCP client
catalog.call {
"slug": "json-query",
"params": {
"json": {
"items": [
{
"name": "a"
},
{
"name": "b"
}
]
},
"path": "items[1].name"
}
}
On the hosted connector at https://agent402.tools/mcp, catalog.call runs json-query free (rate-limited, no wallet). Local install: npx -y agent402-mcp.
Errors and behavior
jsonandpathare required. An input the tool rejects returns an HTTP 4xx whose body carrieserror,tool,expected,requiredandexample, so the caller can correct it.- A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
- Free tier: no outbound network call leaves the server for this tool, so proof-of-work (16 leading zero bits of sha256) pays for it.
- A
GETorHEADto /api/json-query returns the same 402 quote, so the price can be read without a body. - An
Idempotency-Keyheader makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).
Paid call (JavaScript agent)
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/json-query", {
method: "POST",
headers: { "Content-Type": "application/json" },
body: JSON.stringify({
"json": {
"items": [
{
"name": "a"
},
{
"name": "b"
}
]
},
"path": "items[1].name"
}),
});
No wallet? Pay with compute
Fetch a challenge, solve the sha256 puzzle (16 leading zero bits, a fraction of a second of CPU), and resend with the X-Pow-Solution header:
import { createHash } from "node:crypto";
const lz = (b) => { let t = 0; for (const x of b) { if (!x) { t += 8; continue; } t += Math.clz32(x) - 24; break; } return t; };
const c = await (await fetch("https://agent402.tools/api/pow/challenge?slug=json-query")).json();
let n = 0;
while (lz(createHash("sha256").update(c.challenge + ":" + n).digest()) < c.difficulty) n++;
await fetch("https://agent402.tools/api/json-query", { method: "POST", headers: { "X-Pow-Solution": c.token + ":" + n, "Content-Type": "application/json" }, body: JSON.stringify({"json":{"items":[{"name":"a"},{"name":"b"}]},"path":"items[1].name"}) });
Part of these workflows
JSON query is one step in this skill pack, each sold as a single call:
- API investigation - Point at an unknown API endpoint and figure out how to use it: auth scheme, content type, version, rate limits, OpenAPI/Swagger spec discovery, and JSON response structure. The deterministic recon workflow before writing a single line of integration code.
Related tools
CSV to JSON
POST /api/csv-to-jsonParse CSV (quoted fields supported) into a JSON array of objects, using the first row as headers (header=false for array…
JSON diff
POST /api/json-diffDeep-compare two JSON values. Returns a list of changed/added/removed paths (capped at 1000 differences).
JSON flatten/unflatten
POST /api/json-flattenFlatten nested JSON to dot-path keys, or unflatten dot-path keys back to nested JSON. mode: flatten (default) | unflatte…
JSON validate & format
POST /api/json-formatValidate, pretty-print (any indentation, 0-8 spaces), or minify JSON, optionally with object keys sorted. canonical: tru…
JSON deep merge
POST /api/json-mergeDeep-merge two JSON objects (b wins on conflicts; arrays are concatenated).
JSON to CSV
POST /api/json-to-csvConvert a JSON array of objects to CSV. Nested objects are flattened to dot-path columns.