Media
5 items
Description
Mock APIs in Chrome. No server. No setup. No BS. Mock APIs directly in Chrome. No mock server, proxy, Docker setup, or code changes required. Ruse is a local-first API mocking tool for frontend developers and QA engineers building web apps against APIs that are incomplete, unstable, slow, or hard to reproduce. Open Ruse on the tab you are testing, watch real browser requests in the side panel, click a captured URL, and turn it into a local mock rule. Define the response, save it, and keep building. Your app receives the mock response instantly, right in the browser. What Ruse helps you do: - Mock HTTP requests from fetch() and XMLHttpRequest - Create mock rules from captured browser requests - Turn request log entries into prefilled rule drafts - Organize local mock rules into collections - Match URLs by wildcard, exact URL, or regex - Match by HTTP method and request body - Return custom status codes, headers, JSON, raw text, or multipart responses - Add artificial delays to simulate slow APIs and edge cases - Toggle rules on and off without touching your app - View a live request log from the current working tab - Keep mock data local in your browser Ruse is built for the everyday moments that slow product teams down: The backend is not ready yet. The staging API is flaky. You need to test a 500 error, timeout, empty list, or malformed response. You want to build the UI before the real endpoint exists. You need a predictable demo without depending on live infrastructure. Instead of spinning up a separate mock server or rewriting app code, Ruse lets you control API behavior from Chrome itself. Use it for: - Frontend development - UI state testing - QA and regression testing - Demo preparation - Error state design - Offline development - Reproducing tricky network scenarios Ruse is local-first. Your mock rules, collections, and request logs stay in your browser for the current release, and local mocking does not require an account. Build against the API you need, not the API you are waiting for.
rating_count is the Chrome Web Store ratings count, not a written-review count.