Testing

Install the extension.
Open any web page, then open DevTools (F12 or Tools → Browser Tools → Web Developer Tools).
Click the api-medic tab in DevTools. (To test in the dedicated panel, navigate to about:devtools-toolbox.)
In the Network panel, trigger or select any HTTP request — e.g., reload https://example.com. Right-click → "Send to api-medic" (or use the panel's request picker).
The panel transmits that single request as a one-entry HAR to https://api-medic.markandrewmarquez.com/api/analyze and renders the returned diagnostic Report inline.

No login or credentials needed.
Network and data

Sole network destination: https://api-medic.markandrewmarquez.com — domain owned by me.
Backend: AWS Lambda, source in the same public repo at aws/ (referred to in code as "Lambda").
Stateless: no DynamoDB, no S3 writes for user data, no logging of request payloads, no telemetry.
I believe this qualifies for implicit consent under the "Self-Evident, Single-Use Extension" policy: transmission is purpose-bounded and user-initiated (single click on a labeled control), the listing and in-panel UI make the purpose self-evident, and the data scope is limited to the single request the user selects. No persistent identifiers, cookies, or analytics are added by the extension.
data_collection_permissions is declared in the manifest accordingly.

Source build

Source bundle: api-medic-source-0.1.0.zip. Includes BUILD.md with reproducible-build instructions:
cd frontend && npm ci && cd ../extension && npm ci && npm run build && npm run package

Build environment: Node 20.x, npm 10.x.
The dist/ shipped in the .xpi is bundled by Vite/Rollup. Source includes extension/, frontend/src/, and frontend/package*.json. The @frontend Vite alias resolves into frontend/src.
All dependencies install via npm ci from the official npm registry; nothing is fetched from arbitrary URLs at build time.

Privacy policy
https://api-medic.markandrewmarquez.com/privacy
Happy to answer any questions.