Generate the path, then execute
Natural language is easy to overload in one shot. Check that the generated JSONPath points at the right fields, then execute, so you aren't guessing at an empty result.
JSON Tools for AI Developers · Runs locally
Natural language generation · Schema · Zod · OpenAPI · Function Calling · MCP · 30+ tools
If you don't want to memorize JSONPath, say "users older than 25" in English or Chinese, generate a path, then run it.
Paste JSON on the left. Write natural language or $.users[*].name in the query box. Generate path first, then Execute query.
Path conversion is local rules. Complex filters and recursive descent may not be right on the first try. Trust the actual matches.
Copy matched nodes, or keep reading in Tree view or Table.
Natural language is easy to overload in one shot. Check that the generated JSONPath points at the right fields, then execute, so you aren't guessing at an empty result.
If you already write expressions, the JSONPath page is faster. This page is for an ad-hoc question, or a teammate who doesn't know the syntax.
No. Generate a path from natural language first, then tweak a selector or two.
Common field comparisons and array extracts, yes. For multilayer conditions, write JSONPath by hand.
This page adds natural language → path. The JSONPath page is for people who already know the expression.
No.
Yes. The important part is that field names match keys in the JSON.
Wrong path, the value is an object instead of an array, or the filter is too tight. Confirm in Tree view first.
No. Queries are read-only. Results stay on the right.
Execute query returns matched values. Generate path only returns the expression.