{ "schema_version": 1, "generated": "2026-10-20", "id": "reacher-z-awesome-rea--turn-captured-traffic-into-api-spec", "repo": "reacher-z/Awesome-REA", "repo_url": "https://github.com/reacher-z/Awesome-REA", "repo_slug": "reacher-z-awesome-rea", "title": "Turn captured app traffic into an API spec", "page_title": "How to turn captured app traffic into an API spec with Awesome REA", "summary": "Capture HTTP calls from an app, then generate an OpenAPI spec or MCP tools from them.", "who": "An integration developer who needs the API of an app that has no public documentation.", "problem": "Undocumented app APIs have to be mapped by hand from network traffic, which is tedious and error-prone.", "outcome": "A draft OpenAPI 3.1 spec or MCP tool set built from the captured requests, to start an integration.", "steps": [ "Open the mitmproxy entry in the Awesome REA README and set up the proxy on the device or browser you will use.", "Use the app or site you are allowed to test and record its HTTP traffic.", "Remove session tokens, cookies and personal data from the captured file before sharing it.", "Open the Spectral entry and feed the redacted traffic into its LLM-based analysis to generate OpenAPI 3.1, MCP tools or a GraphQL schema.", "Test a few generated endpoints against the live service and correct any that do not match." ], "agent_prompt": "Using mitmproxy and Spectral from the Awesome-REA README, analyze the redacted HTTP capture at from and produce an OpenAPI 3.1 draft in . Note any endpoints that need authentication. Verify two generated endpoints against the live service before reporting success.", "agents": [ "any" ], "difficulty": "Advanced", "time": "1 hour", "basis": "readme", "caveat": "Spectral and the Browser Reverse Engineering Toolkit are listed as separate projects, and their generated output has not been verified by this list.", "category": "Software and DevOps", "tags": [ "Software and DevOps" ], "lang": "python", "requirements": [ "Access to the Awesome-REA README or the linked awesomerea.org directory to choose a tool", "A website, app or captured file that you own or have permission to analyze", "Node.js if you plan to run the Dembrandt CLI", "A browser or proxy tool to capture the traffic or pages you want to study" ], "risk": "dual-use", "seen_in_the_wild": false, "mentioned_publicly": false, "risks": [ { "tag": "credentials", "notice": "Captured traffic often contains session tokens and cookies, so redact them before any file leaves your machine or goes to an agent." } ], "best": false, "score": 0.8, "evidence": [], "url": "https://dedupedai.com/use-cases/reacher-z-awesome-rea/turn-captured-traffic-into-api-spec/", "md": "https://dedupedai.com/use-cases/reacher-z-awesome-rea/turn-captured-traffic-into-api-spec/index.md", "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.", "api": "https://dedupedai.com/api/v1/usecases/reacher-z-awesome-rea--turn-captured-traffic-into-api-spec.json", "api_version": "v1" }