AI 产品解读Intercept, modify, and mock HTTP(S) network requests and responses directly in the Chrome browser
Enables web developers and QA engineers to modify network traffic (redirect URLs, modify headers, inject scripts, mock API responses) without setting up a proxy server, avoiding VPN issues and latency. Allows frontend development when backend APIs aren't ready, testing local JS/CSS changes on production sites, and overriding REST/GraphQL API responses.
User installs the extension, creates HTTP rules (redirect, headers, script injection, mock API responses) via the extension popup or the Requestly web app at app.requestly.io. Rules are stored locally in chrome.storage.local. When browsing, the service worker intercepts matching requests using declarativeNetRequest and webRequest APIs, applies the configured rules, and optionally records sessions for replay. The extension integrates with the Requestly web app for advanced rule management, team collaboration, and cloud sync.
URL redirect rulesHTTP header modification (request and response)JavaScript and CSS injection into pagesREST and GraphQL API response mockingAPI request/response body and status code overrideSession recording and replay
- 目标用户
- Web developers / QA engineers / Frontend developers / DevOps engineers / API testers
- Source code is heavily minified making detailed logic analysis difficult
- Could not definitively determine if the web app UI (popup React app) requires login or renders locally without auth
- The devtools/index.js is 1.69MB minified - deep inspection was not feasible within tool budget
付费分析未识别到付费功能
No payment-related code found in the extension source: no premium/subscription/billing/pricing/upgrade/stripe keywords detected. The 'checkout' matches are all from the rrweb session recording library (checkoutEveryNms, isCheckout parameters) which is session replay checkpoint terminology, not payment. The extension is open source (https://github.com/requestly/requestly/). No feature gating, license checks, or payment UI found in the extension code. The destination service (Requestly/BrowserStack) likely has paid team/enterprise plans, but the extension itself does not gate features behind payment.
- 置信度
- 70
- 支付平台
- --
- 来源
- AI / 中
- 需要登录
- 是
- 登录理由
- The extension's core rule-application engine works locally without login (rules stored in chrome.storage.local). However, the extension heavily integrates with the Requestly web app at app.requestly.io for session recordings (SESSIONS_URL), rule management UI, team collaboration, and cloud sync. The app.cs.js content script injects on requestly domains to bridge the extension and web app. Session recording drafts open at app.requestly.io/sessions/draft/{id}, and the externally_connectable manifest connects to BrowserStack domains. Login to the destination service (Requestly web app) is required for the full workflow including cloud features, session replay, and team collaboration.
Why tf do i need to register in some cloud app just to fiddle with some http headers?
非常难用,想修改一个,单规则配置太单一,多规则顺序不能控制,无法达到预期效果
为什么现在这个插件 趋向于收费了 而且 现在登录有问题 一直选择google或者 email登录都登录不上去
ahora es paga
Was a nice tool before it became paid
Not free.
We used this to delay API responses and modify params received to see how front end would handle them - this allowed front end to re-create a range of scenarios without wasting any back enders time. Did exactly what we needed it to, would recommend
Was good until they decided to paywall a few free feature with a forced overpriced subscription, immediately uninstalled .
Works as it should, but adds its script to every page even in paused state - I don't like this and so have to manually disable it every time I finish working with it. Update: the script is called "libs/customElements.js" and, as I understand it, is part of the "Session Recording" option. It's injected into each page when requestly is enabled (paused or not, it doesn't matter), and even if it doesn't do anything, I generally don't want extensions interfering with pages when I disable them.
I was recently introduced to Requestly and used it for verifying libraries created in Adobe Launch without actually publishing them and I must say it performed perfectly. It is super user friendly and offers great ease of use.