API Network Recorder

API Network Recorder is a developer tool for capturing, inspecting, filtering, and exporting API network traffic directly from Chrome. Use it to debug API integrations, compare requests, inspect response data, document observed endpoints, and generate exportable API references from real browser traffic. An optional Windows integration lets Codex search and analyze captured API calls through MCP. Features: - Capture API-like network requests from web pages. - Inspect request URLs, HTTP methods, status codes, headers, timing, and request and response bodies when available. - Filter captured records by search text, HTTP method, status group, source, host, and API-only mode. Search includes captured bodies. - Group captured traffic by endpoint. - Compare requests to identify differences in headers, query parameters, bodies, status codes, and errors. - Copy requests as cURL commands for Bash or PowerShell. - Export captured records as JSON. - Export grouped endpoints as Markdown documentation. - Export an OpenAPI draft based on observed traffic. - Save filtered requests as named sessions for later inspection. - Pin important requests to preserve them beyond the automatic retention limit. - Pause and resume recording. - Exclude specific tabs or domains from recording. - Choose how many records to retain, with older unpinned records removed automatically. - View capture status across browser tabs. - Store captured records locally in the browser. Optional Codex integration: Open the AI access page for installation instructions, connection status, and recording controls. The separate Windows x64 installer configures the local MCP integration and includes a Codex skill for inspecting captured traffic. Choose read-only access or allow Codex to start and stop recording and deep capture. After installation, restart Codex and keep Chrome open. The AI access page does not need to remain open. You can disconnect the integration from that page or uninstall it through Windows Installed Apps. Deep capture uses the Chrome Debugger Protocol to inspect response bodies when available. When enabled, it applies across eligible browser tabs, including newly opened tabs, while respecting your tab and domain exclusions. Chrome may display a debugger banner while deep capture is active. Captured data is stored locally in the browser. The extension and local integration do not upload captured network data to an external server. If you authorize access through Codex or another AI client, that client may send requested data to its AI provider under its own settings and privacy policy.