What is a JSON Pointer?

A JSON Pointer (RFC 6901) is a compact string syntax for identifying a specific value inside a JSON document. Segments are separated by slashes, so /a/b/0 means "key a, then key b, then array element 0".

How do I reference keys that contain a slash or tilde?

RFC 6901 escapes them: a literal tilde is written ~0 and a literal forward slash is written ~1. The tool decodes these escapes before matching.

How do I select an array element?

Use the numeric index as a segment. /items/2 returns the third element of the items array. An out-of-range index returns no match.

Is my JSON uploaded anywhere?

No. Parsing and pointer evaluation happen entirely in your browser. Nothing you paste is sent to a server.

JSON Pointer Extractor

Extract any field from structured LLM output

Models that return JSON — tool calls, function calls, structured outputs — bury the value you actually want deep inside wrapper objects. This tool lets you pull it out with a single RFC 6901 JSON Pointer, the standard, unambiguous way to address a node in a JSON document. Paste the response, type a pointer like /choices/0/message/content, and get the value back instantly.

How JSON Pointer evaluation works

A JSON Pointer is a string of reference tokens, each prefixed by a /. Starting from the root document, the evaluator walks one token at a time: for an object it looks up the token as a key, for an array it treats the token as a numeric index. The empty pointer "" refers to the whole document. Two escape sequences keep the syntax unambiguous — ~1 means a literal / inside a key, and ~0 means a literal ~. If any token fails to resolve (missing key, out-of-range index), the whole pointer has no match.

Tips and examples

OpenAI chat completions: /choices/0/message/content grabs the assistant text.
Tool/function arguments often arrive as a JSON string — extract it, then paste that string back in as a fresh document to drill deeper.
To pull every element of an array you address them one index at a time; a pointer resolves to exactly one node by design.
If a key literally contains a slash (rare, but valid JSON), escape it as ~1.