Generate OpenAPI 3.1 specifications from recorded browser traffic.
npx skills add https://github.com/browserbase/skills --skill browser-to-api
Please help me install this Agent Skill. Skill: browser-to-api Source: https://github.com/browserbase/skills/tree/main/skills/browser-to-api Command: npx skills add https://github.com/browserbase/skills --skill browser-to-api
This Skill automates the discovery of API endpoints from browser traffic and generates OpenAPI specifications, saving developers time and effort in documenting and integrating with APIs.
Generate an OpenAPI specification for a recorded browser session by running the 'browser-to-api' skill with the path to the browser trace directory.
High-intent search queries and answers about installing and using this skill.
To generate an OpenAPI spec from browser traffic, use a skill that discovers API endpoints from recorded sessions and outputs OpenAPI 3.1 specifications using JSON-Schema inference. You need to provide the path to your recorded browser trace directory.
Yes, you can extract API endpoints automatically from a recorded browser session. The tool analyzes the browser traffic to discover endpoints and infers JSON schemas to document the application's API for backend integration.
Yes, you need Node.js installed to convert browser traces into OpenAPI 3.1 specifications. The process also requires a valid browser-trace run directory containing the recorded session data to parse the API traffic.
Yes, you can filter and redact sensitive information when discovering APIs from browser traffic. The extraction process supports filtering endpoints and redacting sensitive data to ensure the generated OpenAPI specifications are secure to share.
The best way to document an undocumented web application API is by recording a browser session and using an automated discovery tool to extract endpoints. This generates a structured OpenAPI 3.1 specification from the traffic, saving manual documentation effort.
API discovery from browser traffic requires a browser-trace directory because it serves as the input data source containing the recorded network requests. Without this trace directory, the tool has no session traffic to analyze for endpoint extraction and schema inference.
johnlindquistAutomate browser interactions for web testing and data extraction with Puppeteer or Playwright.
Sumeet138Generate and validate OpenAPI 3.1 specifications from code and design inputs.
maxvaegaParse and validate JSON data against schemas and JSONPath queries.
AskTinNguyenInspect live pages, DOM, console logs, and network activity via Chrome DevTools MCP.
