Media
3 items
Description
Mock, redirect, delay or rewrite HTTP requests from the browser. No backend, no account, everything stays on your machine. Net Tinker lets you intercept fetch and XHR requests and change what happens to them — without touching your backend, without an account, and without anything leaving your machine. WHAT YOU CAN DO • Mock a response — return your own status, headers and body. The request never reaches the network. • Change the real response — find and replace text in it, or overwrite a single JSON field and leave everything else exactly as the server sent it. • Modify a real request — change its body, its headers, or its query parameters, and let it go out as usual. • Redirect a request to a different URL, or rewrite part of the URL. • Block a request entirely. • Add latency to any of the above — mocking and slowing down the same endpoint is one rule, not a choice between two — to see how your UI behaves on a slow connection. HIT EXACTLY THE REQUESTS YOU MEAN Match by URL or host — contains, exact, regex or wildcard — then narrow it down by HTTP method, by a request header, by what's in the request body, or by which page is making the call. Paste a real URL into the test box and the form tells you whether the rule would catch it, before you save anything. Pin a rule to a single tab when you don't want it affecting everything else you have open. And because GraphQL sends every operation to the same endpoint, matching on the body is what finally lets you mock one operation without touching the rest. REUSE THE SAME RULES EVERYWHERE Write {{variables}} into bodies, headers, redirect URLs and query parameters, then define environments — Local, Dev, Staging, Prod — that override only the values which actually change. Switch between them from the popup, and the same set of rules follows you from localhost to staging. BUILD RULES FROM REAL TRAFFIC Net Tinker adds a panel to Chrome DevTools listing the requests of the page you are inspecting. One click turns any of them into a rule — and "Mock" fills in the real status, headers and response body for you, so you start from what the server actually returned instead of typing a fixture by hand. GraphQL operation names are detected and shown, so a list of calls to a single /graphql endpoint is finally readable. Any captured request can also be copied as a curl command or as a fetch() call, and the whole session exported as a standard HAR file — with credentials redacted by default, and response bodies left out unless you ask for them. TAKE THE RULES WITH YOU Copy any rule as a Playwright or Cypress mock and paste it straight into your test suite — or copy the whole set at once. Rule types that can't be translated come out as a comment saying why, never silently dropped, and credentials are redacted with the snippet itself telling you what it hid. You can also copy a rule as a curl or fetch() call to the endpoint it intercepts, when what you want is to compare your mock against the real thing. STAY IN CONTROL • Choose where it works: everywhere, only on localhost, or only on domains you list. Outside that scope Net Tinker doesn't touch the page at all — it removes its own patches rather than filtering later — and the toolbar icon says so. • When two rules match the same request, the one lower in the list wins, and you move rules up and down to decide which one that is. • Group rules and switch a whole group on or off in one click. • Select several rules at once to enable, disable, export or delete them together. • See exactly which rule touched which request, whether it reached the network, how much delay it added, and turn the culprit off right there. • Search by name, URL, description or tag. • Export and import rules to share a setup — with an option to strip credentials first, so you don't hand someone your tokens by accident, and a warning when an import would collide with rules you already have. • A built-in help page explains what each rule type does and walks through the reasons a rule might not be firing. • Light and dark themes, following your system setting. PRIVACY Everything is stored locally in your browser. There is no server, no account, no analytics and no tracking. Requests shown in the DevTools panel live only in memory while DevTools is open: nothing is written to storage unless you turn one of them into a rule or export a HAR yourself. Recording a tab is the one feature that does keep a log, and only while you have it switched on: it holds the 200 most recent requests of that tab, locally, and one click empties it. Net Tinker needs broad host access because it cannot know in advance which site you will want to create a rule for. That access is used only to run the rules you configure yourself. It declares two permissions in total: storage, and that host access. Nothing else — no tabs, no scripting, no browsing data. NO LIMITS AND NO UPSELL Every rule type is free, and there is no cap on how many rules you create or keep active. That is worth saying plainly, because it is where comparable tools draw their paid line — the best known one stops you at five rules, three of them active at a time. Useful for testing APIs, simulating backend errors, exercising the loading and error states of your frontend, or debugging an integration without depending on a real environment. Available in English and Spanish.