How to use AI API Response → Potential Issues
- Open the tool and paste an API response (status line, headers and body, or just the JSON).
- Optionally add context (feature description, acceptance criteria, environment) — the more concrete the input, the better the result.
- Pick the options (count, output language, focus) and press the action button.
- Review the structured result in the table, then copy or download it as Markdown, CSV or JSON.
AI API Response → Potential Issues features
- Spots inconsistent types, missing fields, wrong status semantics, leaked data, bad date formats, null handling, naming and pagination smells
- Every issue carries a JSON path and quoted evidence
- Optional expected contract to compare against
- Health score plus "looks good" list
- Choose English, Arabic or Hindi for the generated text — identifiers, HTTP methods and technical tokens always stay in English.
AI API Response → Potential Issues example
Response review
Input:
{"data":[{"id":1,"passwordHash":"…"},{"id":"2","createdAt":"02/01/2026"}]}Output:
ISS-1 data-exposure (Critical) $.data[0].passwordHash
ISS-2 inconsistent-type (High) $.data[*].id — number vs string
ISS-3 bad-date-format (Medium) $.data[1].createdAtFrequently asked questions about AI API Response → Potential Issues
Should I include headers?
Yes when you can — status and headers let the AI check status semantics, content types and caching in addition to the body.
Is my input stored?
No. Your text is sent to the Mutqan AI service and the structured result is returned to your browser. We do not store prompts or outputs — only anonymous usage counters used for daily limits.
How many generations can I run?
Anonymous visitors get a small daily allowance per network address; registered users get a higher daily quota. The remaining count is shown under every result.
Can I get the result in Arabic or Hindi?
Yes — choose the output language. Natural-language fields are written in that language while identifiers, HTTP methods, paths and other technical tokens stay in English.
Technical notes
Your input is sent to the Mutqan AI service over an encrypted connection; prompts and results are never stored — only anonymous usage counters used for rate limiting.
The AI must answer with strict JSON that is validated against a schema on the server before anything is rendered; malformed answers are retried once and then rejected with a clear message.