Frigade - Reverse-engineering web apps into agent tools
Frigade is a browser-based agent that automatically transforms authenticated web applications into powerful tools for AI assistants. By observing how apps call their own APIs, Frigade generates self-updating 'recipes' that include endpoints, authentication methods, and schemas, effectively creating an auto-generated MCP server. This solution eliminates the need for manual API integration or brittle computer-use agents, allowing LLMs to perform complex actions within platforms like Jira, Spotify, and Hacker News directly. Developers can enable deep product integration without writing or maintaining any code, ensuring their AI agents stay synchronized with application changes.
The result is you build a highly skilled AI assistant that actually integrates deeply with any product (not just chat and RAG) with minimal effort.
- hoppp
How do you make sure you are not violating terms and conditions if they forbid injecting third party javascript into the website explicitly?
Does your LLM ingest terms and conditions too?
In some cases in the past, finding and using auth tokens in the front end has resulted in hacking charges, in those cases alleged hacker found an api key in the front end and directly accessed the database, which resulted in a jail sentance.
How do you solve this issue that some companies may become hostile if injected code extracts auth tokens and accesses backend?
- hajimuz
This is really helpful. I usually manually do this with chrome dev tools, it’s kind of tedious especially the header and cookies handling.
- nixus76
Very cool! Does it require some kind of scraping of a third party web app, like clicking through with a browser agent? If so, how can I be sure it does not delete my account or subscribe to another plan or make some other destructive actions if I allow it to do that with my authed acct?
- arjunchint
I am not following a couple of things:
- you sell to websites an in-app agent
- why not just have them give you API spec, why reverse engineer their APIs?
A bit longer term, would you see yourself competing with WebMCP then? Because the website can just expose those APIs to any browser agent
- quarkcarbon279
I'm so surprised you didn't add your agent on your own website? And the same fundamentals of a browser agent why you can't achieve everything with APIs alone apply here too inside a website. What's your take?
We have been building in the space balancing both with priority to GUI tools currently building on top of the great GUI experiences of a product, rtrvr.ai/rover