R
Show HN
Show HN: Rover – Embeddable web agent
Rover is the world's first Embeddable Web Agent, a chat widget that lives on your website and takes real actions for your users. Clicks buttons. Fills forms. Runs checkout. Guides onboarding. All inside your UI.

One script tag. No APIs to expose. No code to maintain.

We built Rover because we think websites need their own conversational agentic interfaces as users don't want to figure out how your site works. If they don't have one then they are going to be disintermediated by Chrome's or Comet's agent.

We are the only Web Agent with a DOM-only architecture, thus we can setup an embeddable script as a harness to take actions on your site. Our DOM-native approach hits 81.39% on WebBench.

Beta with embed script is live at rtrvr.ai/rover.

Built by two ex-Google engineers. Happy to answer architecture questions.

  • nusl
  • ·
  • 11 hours ago
  • ·
  • [ - ]
Code written by LLMs, website copy written by LLMs trashing competitors, Hacker News post written by LLMs, as if it were for LinkedIn. AI images everywhere. I dunno man, this is really sloppy.
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 underlying agentic performance though is undeniable.

Also like whats the point if something is AI generated, we do thorough review to ensure readibility, coherence and accuracy.

  • nusl
  • ·
  • 47 minutes ago
  • ·
  • [ - ]
I don't agree that it's possible to output this much code with an LLM and also be sure that you know the codebase. Chances are very close to 100% that the entire stack is vibe coded and you rely on LLMs to fix bugs too
  • ·
  • 7 hours ago
  • ·
  • [ - ]
This isn't a ______. This isn't a ______. This is ______.

The message is clear: ______ isn't a nice-to-have. It's a ______.

But here's what nobody's talking about: ...

I can't force myself to spend more thought reading than was spent writing.

Thanks for the feedback!

We completely rewrote our launch blog post and included a demo video of the embedded agent live!

  • ·
  • 7 hours ago
  • ·
  • [ - ]
We have seen people hire consultants to build RAG pipelines, maintain them only to be QA Agent when the world is shifting losing traffic to the likes of ChatGPT and Google comes up with a protocol that makes you do more work with WebMCP essentially maintain a lot of APIs for your UI and DBs. Rover is the answer to these painpoints. No RAG pipelines, just one script tag your users engage, retain, get work done on your website without ever leaving it and fully conversational.
Essentially, are you saying 'dont give data to Google, but give to us'? I can't see how the merchant websites own anything given that the script points to your website and everything else is a blackbox. Just wondering...
Hey, we have various configurations available even in this very early preview: https://rover.rtrvr.ai/docs/configuration and you can turn off telemetry so we don't collect the data . As a website you can also configure to host the script on your preferred endpoint and our 'apiBase' helps with that pointing to custom domains. And based on project data needs we are also open to tighter data policy rules.
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/recommendations) outside of your control. - we want to be long term partners to websites to craft the agentic experience between them and their users