AI agents should browse your site, not call your API

Name: AI agents should browse your site, not call your API
Availability: InStock
Author: quarkcarbon279

by quarkcarbon279·Apr 17, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●MidBold BetSlick

DOM-native agents bypass API maintenance, but it's a SaaS pitch in a crowded chatbot market.

Strengths

•Architectural argument against RAG staleness and API maintenance tax is well-reasoned.
•Uses existing site IAM and session state instead of syncing parallel data.
•Claims 2,000+ live integrations suggest the approach works in production.

Weaknesses

•Links to a blog post, not an interactive demo or open repository.
•Competes directly with Intercom, Drift, and dozens of established support bots.

Post Description

We compared four architectures for putting AI agents on websites — RAG bots, API-tool agents(WebMCP), code-writing sandboxes (Cloudflare Agent Lee), and DOM-native execution. Three of them force you to maintain a parallel engineering surface. The DOM already has live state, user auth, and permissions baked in. A structural breakdown of why.