Capture the inspected page’s traffic. Analyze the waste locally.
A Manifest V3 DevTools extension plus a standalone HAR analyzer. It measures metadata bytes, duplicate payloads, request families and vendor-reported AI token usage — entirely in your browser, with secrets redacted before anything is rendered or exported.
Two paths: chrome.devtools.network.getHAR() + onRequestFinished in the panel, or chrome.debugger with Network.enable for one-click capture. Both build a HAR 1.2 log in memory, response bodies included when getContent()/getResponseBody() allows.
What the engine computes
Per-entry header/metadata bytes vs. body bytes, duplicate payload candidates by body hash, addressable waste, request families by normalized path, telemetry event types, header leaders and endpoint waste ranking.
Token extraction, not guessing
usageMetadata.promptTokenCount / candidatesTokenCount (Gemini, Vertex), usage.prompt_tokens / completion_tokens (OpenAI, Azure), input_tokens / output_tokens / cache_read_input_tokens (Anthropic). No model identified → tokens shown, no cost invented.
Evidence strength, never assertion
Confirmed / strong / possible / not evidenced. Proxy, sidecar and mesh hops are labelled by what the HAR can actually prove; Kubernetes ownership is explicitly out of reach.
Runtime
Manifest V3, no build step, plain ES5-safe JS modules (engine.js, render.js, store.js). IndexedDB for saved baselines and comparison runs. Same engine file powers the extension and the web analyzer.
Exports
Sanitized HAR, waste report JSON, audit CSV/JSON, per-request cost CSV/JSON, and print-to-PDF summaries. Redaction runs before serialization, not at render time.
What Deeproq does not touch
No network egress — zero requests leave your browser; there is no Deeproq backend.
No account, no login, no telemetry, no analytics beacon in the extension.
Authorization, Cookie, Set-Cookie, api-key, DD-API-KEY and any header matching token/secret/key/credential are replaced with [REDACTED] before anything renders or exports.
Query-string secrets (key=, access_token=) are stripped from every URL Deeproq stores or prints.
No content scripts injected into your pages; no host_permissions wildcard for reading page DOM.
chrome.debugger attaches only to the tab you explicitly start capture on, and detaches on Stop.
Every stage after capture is pure client-side JavaScript. Redaction sits between capture and analysis, so no unredacted value ever reaches the dashboard, storage or an export.
Try it in one click
The analyzer opens with a drop zone and a paste box. Drop a .har (DevTools → Network → Export HAR), or paste HAR JSON. You get bytes, families, endpoint waste and evidence labels immediately — cost views, baselines and exports are one tab away, not in your face.
Extension is desktop-only; the analyzer runs anywhere, including phones.
Install (unpacked)
1Download and unzip deeproq-extension.zip.
2Open chrome://extensions in Chrome, Edge, Brave, Arc or Opera.
3Enable Developer mode in the top-right corner.
4Click Load unpacked and select the unzipped folder.
5Pin Deeproq from the extensions puzzle-piece menu.
Live capture: toolbar icon → Start capture (uses chrome.debugger; Chrome shows its debugging banner while recording), or DevTools → Deeproq panel → Start Capture. Close DevTools first if Chrome refuses the debugger attach on that tab.