api-medic
Diagnose HTTP requests captured in DevTools — analysis runs on the api-medic hosted demo.
As of June 2026, api-medic has — users in the Developer Tools category.
Usersno change0%
—
—
Ratingno change0%
—
— reviews
Reviewsno change0%
—
Version
0.1.0
Manifest V3
History
1 snapshotsTracking since May 2, 2026.
Not enough history yet for this metric — the chart fills in as we collect more snapshots.
View as table
| Date | Users | Rating | Reviews | Version |
|---|---|---|---|---|
| May 2, 2026 | — | — | — | 0.1.0 |
| Now | — | — | — | 0.1.0 |
Permissions & access
- Permissions
- None declared
- Host access
- https://api-medic.markandrewmarquez.com/*
Screenshots
About
api-medic is an HTTP API troubleshooting tool that lives in your browser's DevTools. When an API request misbehaves — fails TLS, returns the wrong content-type, hits a CORS wall, or just runs slowly — open the api-medic panel, pick the request from the captured list, click Analyze, and read a plain-English diagnostic report. How to use it 1. Open DevTools (F12 or right-click → Inspect). 2. Switch to the "api-medic" tab alongside Network and Console. 3. Reproduce the request — refresh the page, click the broken button, etc. The panel captures it automatically. 4. Select the request, click Analyze, and the diagnostic report appears inline. What it diagnoses - TLS handshake failures and certificate issues, including upcoming expiry - DNS resolution failures - Redirect loops and excessive redirect chains - Auth header issues — expired or malformed JWTs, malformed Authorization headers - Content-type mismatches between request and response - Slow responses, with a breakdown of where time was spent - Malformed JSON payloads - CORS misconfiguration — preflight failures, missing or incorrect headers - Rate limit responses and Retry-After interpretation - Body / status-code inconsistencies Privacy — please read before installing Analysis runs on a hosted demo server (api-medic.markandrewmarquez.com), not locally in your browser. When you click Analyze, the selected request — URL, headers, bodies, and timing — is sent to that server. The server is stateless: nothing is persisted, no database writes, no logs of request bodies. If you don't want to send captured traffic to an external server, the same analyzer runs as a local web UI and CLI from the GitHub repo. Open source, MIT licensed The full source — extension, web UI, CLI, and analysis engine — is at https://github.com/marky224/api-medic. The audience this was originally built for is technical support engineers triaging customer-reported API issues, but the tool is general-purpose: it works on any HTTP(S) request DevTools can see. Privacy policy: see PRIVACY.md in the repo. Source: https://github.com/marky224/api-medic
Technical
- Version
- 0.1.0
- Manifest
- V3
- Size
- 55.86KiB
- Min Chrome
- 102
- Languages
- 1
- Featured
- No
Metadata
- ID
- fhopbgedlmhdfbmnljihdfiijnmdjdoe
- Developer ID
- u92bfb6f2e5622a3179db14d651a1409b
- Developer Email
- [email protected]
- Created
- May 1, 2026
- Last Updated (Store)
- May 1, 2026
- Last Scraped
- Jun 7, 2026
- Website
- —
- Support URL
- https://github.com/marky224/api-medic/issues
- Privacy Policy
- https://api-medic.markandrewmarquez.com/privacy
Data sourced from the Chrome Web Store · last verified Jun 7, 2026.