Which providers does this support?

It auto-detects OpenAI chat completions, the Anthropic Messages API, and Google Gemini generateContent responses. It looks for the characteristic fields of each — choices for OpenAI, content blocks for Anthropic, and candidates for Gemini — and falls back gracefully if the shape is unfamiliar.

Does my response data leave the browser?

No. All parsing happens locally in your browser with no network calls. You can safely paste responses that contain private content because nothing is sent anywhere.

Why is my message content showing as escaped text?

Raw API responses store the text with JSON escaping for newlines and quotes. This tool unescapes it and renders real line breaks, so a response that looked like one long string becomes properly formatted paragraphs and code.

How are tool calls displayed?

When the model returns function or tool calls, the tool name and its JSON arguments are extracted into a separate section and pretty-printed, so you can verify the arguments are valid JSON before executing them in your application.

LLM Response Formatter

Turn a wall of escaped JSON into a readable answer

When you call an LLM API directly, the response is a deeply nested JSON object with the actual message buried inside, escaped newlines, token usage, finish reasons, and possibly tool calls mixed in. This formatter takes that raw body, detects whether it came from OpenAI, Anthropic, or Gemini, and pulls everything apart into clean, labeled sections so you can read the answer and debug the call.

How it works

Paste the full JSON response. The tool inspects the top-level shape to identify the provider: OpenAI responses have a choices array, Anthropic responses have a content array of typed blocks, and Gemini responses have candidates. It then extracts the assistant’s text, unescapes the newlines and quotes so the content renders as real paragraphs, and surfaces the token usage and finish reason. Any tool or function calls are isolated and pretty-printed in their own block.

Tips and notes

This is purely a client-side parser — nothing you paste is sent anywhere, so it is safe for sensitive responses. If the JSON does not match a known provider, the tool still shows you the parsed object and any string fields it can find, which is useful for custom gateways or proxied APIs. When debugging structured output, check the tool-call section to confirm the model returned valid JSON arguments; malformed arguments are the most common cause of downstream failures.