Run a bounded RFC 9535 JSONPath subset with ordered node results, normalized paths, explicit no-match states, limits, and unsupported filters.
Choose your path
Run one bounded documented subset of RFC 9535 against a parsed JSON value and return an ordered node list with normalized paths, explicit no-match behavior and unsupported-selector errors.
Reproduce one exact expression against a versioned response example.
Enter JSON and a root-based query, inspect ordered normalized paths/values and save all three Project fields.
Can compare the selected node list with the consumer contract.
Distinguish zero matches, malformed syntax, unsupported filters, union/slice behavior and caps.
Exercise each supported selector and rejection boundary, then record cardinality and warnings.
No legacy dotted lookup or partial feature is presented as full JSONPath.
Operate query, editor, results and copy/save actions without formatter-first clutter.
Use named controls and textual statuses at desktop and exact narrow width.
Reads every result path/value and error without color-only meaning or overflow.
Outputs and checklists are planning aids. Review the linked current authorities and the records, terms, instructions, and requirements that apply to your exact situation before a consequential decision.
This tool is part of these guided projects. Each project provides step-by-step instructions with checklists and all the tools you need in one place.
Tools you might need next
Compare two JSON objects and highlight differences. Find added, removed, and changed fields. Free developer utility that runs locally in your browser — fast
Validate, losslessly format, and minify JSON while flagging duplicate members and precision-sensitive numbers before parsed tree or XML views.
Infer TypeScript interfaces or aliases from a JSON sample, merging object arrays and exposing optional, readonly, precision, and runtime limits.
The query runs against an ECMAScript-parsed JSON value. Duplicate names or precision-sensitive numbers are reported because parsed results are not lossless source evidence.
Supported RFC 9535 child, wildcard, union, slice and descendant selectors return ordered nodes with normalized paths and a distinct valid-no-match state.
Filter selectors and extension functions are rejected explicitly. Result and traversal caps protect the browser and are displayed as part of the query contract.
Updated: July 2026
An API developer runs a documented query against a versioned response and saves both normalized paths and values for review.
A reviewer checks whether the query returns zero, one, or many ordered nodes and whether that matches the consumer contract.
A documentation owner records the exact expression, sample version, supported selectors, limits, and unsupported filters.
Query one parsed JSON value with documented child, wildcard, union, slice, negative-index, and descendant selectors; filter extensions are rejected rather than approximated.