Inspect API responses and build requests.
Inspect JSON or SSE, prepare a redacted report, or build a request. These local tools need no API key.
Inspect a response.
Your inspection result
Paste a response and choose Inspect response.
Only have an error message or a partial response? Learn how to capture the full API response.
Read the JSON troubleshooting guideInput formats and limits
Checks choices[0] in a non-streaming response. Paste the response body, not an API key. Responses API objects are not supported. A complete capture beginning with HTTP/ is detected automatically: the status and headers are counted, then the JSON or SSE body is routed to the matching inspector. The original paste stays unchanged.
Examples and fixtures
Handwritten samples; no request is sent.
Run the 25-fixture self-testInspect tool-call SSE
Rebuild Chat Completions function calls by index. Nothing is executed or sent to an API.
Your inspection result
Paste the SSE response body and choose Inspect tool calls.
Need to capture the original body first? Follow the capture guide.
LOCAL TOOL · JSON + SSE
Compare two responses.
Compare choice 0 text, finish reason, tool-call counts and usage from captured Chat Completions responses. Matching fields do not prove a complete or correct response.
Both inputs stay in this tab. The comparison makes no network request, model call, or upload.
Configure this provider route
EXACT PROVIDER ROUTE
Prefill route & model ID only
Xiaomi MiMo API · OpenAI-compatible Chat Completions
The route and model ID below were prefilled from this result. This page makes no provider API request.
Confirm this URL matches your provider account before using its key. For the Bash or zsh command, set PROVIDER_API_KEY in the same terminal. No API key is entered or stored here.
https://api.xiaomimimo.com/v1/chat/completions{
"model": "mimo-v2.6-pro",
"messages": []
}cURL works, but your app returns 404?
Compare the actual request URL from your log with the full endpoint in your working cURL or provider docs.
Stays in this tab; no request is sent or saved. Query values and fragments are hidden in results. Remove credentials before pasting.
Compare requests: cURL works, but the app fails?
Compare a working command with one copied from the failing app or its HTTP capture.
Parsed in this tab only. Commands are never run, sent or saved. Results hide endpoint values, all header values, message content and unknown JSON fields. Clear the inputs when finished.
Check a request body
Check how a body fits ChinaGenAI’s Chat Completions request rules.
Extract JSON body from cURL
Files, stdin, multiple data arguments, body expansion and unsupported shell syntax need the final JSON body instead. cURL data options.
Nothing leaves this tab
The checker runs locally. It does not call the API, save your text or repeat it in the result.
Check supplier-quote fields
Fictional source for the example:
Example only: Cedar offers 250 units at USD 5.20 each, MOQ 200, EXW Ningbo. Payment: 30% deposit, 70% before dispatch. Lead time is not stated.
The starting JSON is handwritten example data, not a live model response. This checker validates fields and types, not whether a model’s claims are true.
Text stays in this page’s memory. It is not uploaded or saved by the checker.