Get the root right first
Some responses wrap in data or result. Miss one level and you get empty. Use Tree view when you are unsure, then write the path.
JSON Tools for AI Developers · Runs locally
Natural language generation · Schema · Zod · OpenAPI · Function Calling · MCP · 30+ tools
The API doc says $.data.list[*].id, and hunting through the response by hand is slow. A path pulls matching nodes in one shot.
Paste JSON on the left, write $.users[*].name in the path box, click Query.
Common dots, indexes, and wildcards are covered. If a filter looks wrong, fix the path against Tree view.
The query runs locally. Responses with personal data don't need to be redacted first.
Some responses wrap in data or result. Miss one level and you get empty. Use Tree view when you are unsure, then write the path.
$.users[*].name pulls every name. Use [0] for the first only. If a filter is wrong, widen first, then tighten.
Dot access, array indexes, * wildcards, and common filters. Rare implementation details follow this page's result.
Wrong path, different field-name case, or the value is an object instead of an array. Confirm in Tree view first.
Use this page if you already write paths. Use NL Query if you want natural language first.
No.
It means the root. Most expressions are less ambiguous if they start with $.
No. Copy the result and edit it yourself.
Common comparisons, yes. Split especially complex predicates into two steps or use a script.
It follows traversal order. Don't treat this as a sort tool.