81–90 of 97 posts
Hey Alex, we had similar thoughts at Retriever AI of moving from webpage interactions to reverse engineering the underlying APIs. Compared to your our approach, we are doing this entirely within a browser extension so meeting users where they already doing their existing work. Within the extension just record doing a task, we reverse engineer the APIs and write a script. Then execute the script from within the webpag…
Congratulations on the launch. Totally unrelated, I am just curious about why you chose the name, as someone who is Ugandan and was born in raised in Kampala (which is the Capital City of Uganda BTW). Congratulations again.
just looking for what is USP(unique selling point) here
happy for you though if this actually works
Earlier quoted context omitted.
Some people may believe in equal measure that intentionally trying to break interoperability is unethical. Especially if it's my data.
show me one ToS for any major service that has "interoperability" in their clauses. "interoperability" is never the case in the agreements. it is very stupid decision from business perspective. and unless legally required (like in agriculture or something, "right to repair"), no sane business will provide this to their customers.
I will concede your observation that often businesses act unethically if it means they get more money.
But, ethics doesn't mean "obey the ToS", it means structure the ToS such that the ToS itself is ethical. In my opinion (which is equal in value to yours), banning interoperability in a ToS is even less ethical than violating such an unethical ToS.
For a clue as to why that is, ask why "right to repair" exists as a concept. What are the ethical principles underlying "right to repair"? After all: like you say, companies could make more money by forbidding it in their ToS (and have).
Prety cool, are you able to output a openapi or similar spec? I tried my hand at this once from har file, build a DAG of the requests and responses and how their parameters map into each other, and then try to build a spec. But it was very brittle. I imagine now with LLMs its much more viable. I always thought generating clients and load tests would be a cool use case.
Hey Alex, we had similar thoughts at Retriever AI of moving from webpage interactions to reverse engineering the underlying APIs. Compared to your our approach, we are doing this entirely within a browser extension so meeting users where they already doing their existing work. Within the extension just record doing a task, we reverse engineer the APIs and write a script. Then execute the script from within the webpag…
Interesting , I am curious how this gonna reverse engineer a perfect webapp that have many guards like captcha,cookies,auth.etc just looking for what is USP(unique selling point) here happy for you though if this actually works
Earlier quoted context omitted.
sorry a bit confused on your question here. If you're asking about JSON RPC we handle this via parsing. The AI can then handle deducing structure most of the time given enough context
ya, unless its very trivial, AI won't be able to "deduce the structure most of the time".