API Documentation Audit for Developers
Check examples, errors and versioning information.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Audit API documentation. Paste endpoint descriptions with examples, authentication instructions and error tables: [API_DOCS]. Typical integrator and their goals: [INTEGRATOR_GOALS]. Support questions received: [SUPPORT_QUESTIONS]. Check whether a developer can make a first successful call in ten minutes, whether examples are complete and correct, errors are explained with fixes, rate limits and versions are stated, and changelogs exist. Compare with the support questions to find gaps. Return a table with Page, Problem, Severity (red, amber, green) and Fix, a getting-started outline, and a list of examples to add. Also check the page structure for scanning, the use of copyable examples in more than one language, and the presence of a changelog and deprecation notices. Suggest a feedback link on each page and a monthly review of the most visited and the most complained about pages. Finish with a list of questions to ask three developers who recently integrated, covering where they got stuck, what they searched for and what they wish had been on the page.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.