API TRIAGE Browser-only

OpenAI-compatible API diagnostics

Turn a failed request into a safe next test.

Choose the symptom, inspect a redacted configuration, and get a bounded troubleshooting plan. Nothing leaves this browser.

1. Describe the symptom

Safe inputs only

Do not include an API key, query string, or signed URL parameter.

Remove keys and user content first. The report will redact common token patterns again as a safeguard.

2. Diagnose safely

Your next steps

Start with the smallest test

Confirm the base URL and model discovery before a long prompt, batch job, streaming connection, or production retry loop.

Keep retries bounded

For rate limits and temporary failures, reduce concurrency and use a finite exponential backoff. Never retry authentication or malformed-request failures blindly.

Log signals, not secrets

Keep the timestamp, host, path, status, duration, and local trace ID. Do not log authorization headers, raw prompts, or `.env` snapshots.