arjunchint

6 ms·

31.
by arjunchint 6mo ago
Yea would love to try out the extension! ITs always interesting to see everyone's design approach. I really don't want to install an app on to my laptop, especially an MITM, so I think extension would be better.
32.
by arjunchint 6mo ago
The tool: https://www.rtrvr.ai/ Our recent technical write up on network discovery/ranking/codegen: https://www.rtrvr.ai/blog/ai-subroutines-zero-token-determin...
33.
Show HN: AI Subroutines – Run automation scripts inside your browser tab(rtrvr.ai)
46 points by arjunchint 6mo ago|17 comments
34.
by arjunchint 6mo ago
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 th
35.
by arjunchint 6mo ago
Really do think that spreadsheets are the most optimal way to coordinate agents. Each row spins up a parallel agent, columns mapped as input, agent executes and writes new columns as output. We tried initial implementation of this with rtrv
36.
by arjunchint 7mo ago
We built out RoverBook as a fun idea from a DeepMind x Vercel hackathon: what if agents can leave comments/notes/reviews on websites and then surface these in a PostHog like analytics dashboard. - agentic visitors to your site can
37.
Show HN: RoverBook – Moltbook for Your Website(github.com)
3 points by arjunchint 7mo ago|1 comments
38.
by arjunchint 7mo ago
Also PageAgent's DOM based understanding is pretty simple and based on top of Browser-Use's approach. On the other hand we construct our own custom Agent Accessibility Trees to represent webpages to models. This approach leads to
39.
by arjunchint 7mo ago
Every website is just a wrapper around an API: GraphQL mutations, JSON endpoints, paginated XHR. The data layer is cleaner than anything you'd get from DOM parsing. The hard part of raw HTTP scraping was always (1) finding the endpoint
40.
Show HN: Reverse-engineer any site's API from inside the browser(rtrvr.ai)
5 points by arjunchint 7mo ago|1 comments
41.
by arjunchint 7mo ago
I actually tried out PageAgent it was reaaaally slow, and not that accurate. You can actually try it out on our own site rtrvr.ai
42.
by arjunchint 7mo ago
With our rtrvr.ai Extension we are actually about to allow anyone to do this with just prompting: - the agent takes actions on a page - network calls recorded - agent writes script to hit endpoints directly at scale - requests made from mai
43.
by arjunchint 7mo ago
Wild conspiracy theory: this is targetting to decrease usuage from Indian users. There is no way 5-11 AM PT is peak traffic
44.
by arjunchint 7mo ago
Just need to download some more memory
45.
by arjunchint 7mo ago
RIP @FireCrawl or at the very least they were the inspiration for this?
46.
by arjunchint 7mo ago
We are about to open source next week!
47.
by arjunchint 7mo ago
Oh whoa, we are working in parallel on a similar angle! We just launched Rover ( https://rover.rtrvr.ai/ ) as the first Embeddable Web Agent. Similar principles, just embed a script tag and you get an agent that can type&#x2F
48.
by arjunchint 7mo ago
There have been thousands-millions of proposals since the dawn of the internet that got nowhere. To exist is to recognize the material constraints of reality; there are things humans won't ever discover. Ergo we have to prioritize what
49.
by arjunchint 7mo ago
> You say it like it's a bad thing. But ideally this also brings clarity & purpose to your own API design too! Ideally there is conjunct purpose! And perhaps shared mechanism! I update my website multiple times a day. I want to
50.
by arjunchint 7mo ago
So... an API? Most sites don't want to expose APIs or care enough about setup and maintenance of said API.
51.
by arjunchint 7mo ago
Majority of sites don't even expose accessibility functionalities, and for WebMCP you have to expose and maintain internal APIs per page. This opens the site up to abuse/scraping/etc. Thats why I dont see this standard going
52.
by arjunchint 8mo ago
Honestly seeing throttling of AI usuage across all providers: - Google reduced AI Studio's free rate limits by 1/10th - Perplexity imposing rate limits, card filing to continue free subscriptions - Now Anthropic as well There has
53.
by arjunchint 8mo ago
We are still thinking through on the optimal usecases. Right now you can configure blocklists on url paths that the agent won't work on. On the reliability front we offer integrations like Recordings to ground the agent on trajectories
54.
by arjunchint 8mo ago
So with the rise of cloud browser agents, identity management is a critical problem. There are a lot of users on our rtrvr.ai/cloud platform wanting to automate sites where they have to login to and right now are resorting to including
55.
by arjunchint 8mo ago
Thanks for taking a look! So our core technical moat is building up an agentic harness that can represent and take actions on any webpage without any screenshots. With this approach we even beat custom trained models like OpenAI Operator an
56.
by arjunchint 8mo ago
Didn't Anthropic say Claude Cowork was completely written by Claude Code and hence "vibe-coded"? All that matters is that the deliverable agent works seamlessly without bugs/issues, which our web agent excels at even bea
57.
by arjunchint 8mo ago
If the agent is in your site you are at much less mercy of Google's agent to: - redirect users to another site - the user's focus is shifted from your site to whats going on in the agentic chat (in which Google can serve ads&#x2
58.
by arjunchint 8mo ago
Thanks for the feedback! We completely rewrote our launch blog post and included a demo video of the embedded agent live!
59.
by arjunchint 8mo ago
We are firing on a lot of cylinders building out a platform across a browser extension, cloud dashboard, API, and now embeddable web agents. We are a team of two leveraging AI to 100x our output and build out all of these surfaces. The unde
60.
Show HN: Rover – Embeddable web agent(rtrvr.ai)
32 points by arjunchint 8mo ago|18 comments

More ›