3 items
Capture the active tab's API traffic and turn it into a working API client with route-reveal. Turn any website's undocumented API into working, tested code — just by browsing it. Most APIs you need to integrate with were never meant to be public. There's no documentation, no OpenAPI spec, nothing but a bunch of XHR calls your browser makes while you use the site. Today that means opening DevTools, exporting a HAR file, and manually piecing together endpoints, headers, and auth by hand. route-reveal capture skips all of that. Click Start, use the site normally — log in, click around, do whatever you'd do anyway — then click Done. The extension captures every API request and response your browser actually made (not just a guess at the shape of the API) and hands it to route-reveal, which turns it into: - A working client script (Python, JavaScript, or TypeScript) written and tested against the real API - An OpenAPI 3.0 spec and Postman Collection, generated directly from the captured traffic - Plain-text cURL commands, one per request - Optionally, an SDK in Java, C#, Go, PHP, Ruby, or C Why use the extension specifically: it captures traffic from a tab you're already using, in your own logged-in browser session — no separate browser window, no re-entering credentials, no VPN or internal-network complications. If a site is behind a login, a corporate VPN, or otherwise isn't reachable from a cloud browser, this is the path that works. What it needs: a route-reveal account (currently invite-only while in testing) and its API token, pasted into the extension once. From there, it's Start, browse, Done. Permissions, plainly: the extension reads network traffic only on the tab you explicitly start a capture on (chrome.debugger — the only API that can read response bodies under Manifest V3), sends that traffic to your own route-reveal backend, and optionally shows a small on-page status control while capturing (permission requested per-site, only when you start a capture there — never a blanket grant). Nothing else is touched, and nothing runs in the background when you're not actively capturing.
Jul 22, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.