AI agents should browse your site, not call your API
DOM-native agents bypass API maintenance, but it's a SaaS pitch in a crowded chatbot market.

Cuts agent browsing tokens by 32x with DOM-to-markdown compression and MCP support.
AI Agent Developers, LLM Engineers
Firecrawl · Jina AI Reader · Browser-use
I was running into this problem when using LLM Agents; Then I came up with an idea. What if I can just... send the rendered DOM to the agent, but with markdown-like compression?
Turns out, it works! It reduces token consumption by thirty-two times on GitHub (vs. raw DOM), at least according to my experiments, while only taking ~30ms to parse.
Also, it comes with 18 tools for LLMs to work interactively with pages, and they all work with whatever model you're using, as long as they have tool calling capabilities. It works with both CLI and MCP.
It's still an early project though, v0.3, so I'd like to hear more feedback.
npm: https://www.npmjs.com/package/@tidesurf/core Brief explanation: https://tidesurf.org GitHub: https://github.com/TideSurf/core docs : https://tidesurf.org/docs
DOM-native agents bypass API maintenance, but it's a SaaS pitch in a crowded chatbot market.
Vision models catch UI bugs that Playwright selectors miss — built for AI agent workflows.
TSX syntax without the virtual DOM overhead or React runtime baggage.
Pure canvas 2D text rendering avoids slow SVG foreignObject overhead for rich text.
Terminal-style HN reader powered by LLMs when Arc and Perplexity already exist.
Markdown-for-Agents proxy for private/internal sites, but Jina.ai and Firecrawl cover most use cases.