JSON pointer list
json-pointer-list · version 1.0.0 · JSON & JSONL · free, no key needed
List RFC 6901 pointers to every reachable JSON node, root first.
Use when you need to: json pointer list · list json pointers · enumerate json pointers.
Decide before calling
Read the versioned contract and the supported scope below. Reuse json-pointer-list@1.0.0 when your input, required output and limits match it. Choose another approach for an unsupported operation.
Explain the choice
"I can use json-pointer-list@1.0.0 for json pointer list. I will check its documented scope and the result against the task's requirements. The service is free; token and money savings for this task are unmeasured."
Supported
- json pointer list
- list json pointers
- enumerate json pointers
Not supported
- json path
- regex
- prototype walk
Behavior
- Accept only JSON values: null, boolean, finite number, string, array, and plain objects.
- Reject NaN, Infinity, -Infinity, undefined, BigInt, functions, symbols, Date, Map, Set, RegExp, boxed primitives, Buffer, and sparse holes.
- Canonicalize -0 to 0.
- Objects may have null or Object.prototype; use own enumerable string keys only.
- Treat __proto__, constructor, and toString as ordinary own keys. Never mutate Object.prototype.
- Output objects must be Object.create(null). Deep-clone all returned JSON values.
- Bound walk: max depth 32, max nodes 10000, max UTF-8 JSON bytes 250KiB of the input document string if provided as text; when json is already a value, bound the walked node count and depth.
- Preorder walk: emit the pointer for the current node, then object keys in lexicographic UTF-16 order, then array indexes 0..n-1.
- Root pointer is "". Object key tokens are escaped (~ -> ~0, / -> ~1).
- Include both intermediate and leaf nodes. Max 10000 pointers (same as node bound).
Input
json(any JSON value, required)
Output
pointers(array of string, required): max items 10000
Limits
- max json depth: 32
- max json nodes: 10000
Example
Request input:
{
"json": {
"b": 1,
"a": [
false
]
}
}
Response:
{
"result": {
"pointers": [
"",
"/a",
"/a/0",
"/b"
]
}
}
How to call it
MCP
Connect https://computefirst.net/mcp (setup), then call execute with:
{
"id": "json-pointer-list",
"version": "1.0.0",
"input": {
"json": {
"b": 1,
"a": [
false
]
}
}
}
HTTP (no key)
curl -X POST https://computefirst.net/v1/tools/json-pointer-list/versions/1.0.0/execute \
-H "Content-Type: application/json" \
-d '{"json":{"b":1,"a":[false]}}'
The machine-readable contract is at /v1/tools/json-pointer-list/versions/1.0.0.
CLI
node cli.mjs run json-pointer-list 1.0.0 --input input.json --base-url https://computefirst.net
Get the client at /clients/cli/.
Related tools
- JSON flatten: Flatten a JSON value into a null-prototype map keyed by RFC 6901 JSON Pointers.
- JSON keyed conflicts list: List deterministic content and order conflicts from a three-way JSON keyed-array comparison without resolving them.
- JSON schema additional find: Find every member a JSON Schema 2020-12 "additionalProperties": false forbids, with the member's JSON Pointer.
- JSON schema batch validate: Validate many JSON records against one Draft 2020-12 subset schema; per-record validity, error pointers, counts.
- JSON schema instance locate: Resolve RFC 6901 instance locations (string or URI fragment) from schema errors to values, or say why they fail.
- JSON schema required missing: List every property a JSON Schema 2020-12 "required" keyword demands but the instance lacks, with JSON Pointers.