How Onto Works
One edge layer. Two representations. Every AI agent gets clean, semantic content while humans see the full experience — zero code changes.
AI agents are drowning in your React bloat
When GPTBot, ClaudeBot, or Perplexity crawls your Next.js site, they download hundreds of kilobytes of HTML, CSS framework classes, JavaScript bundles, and layout wrappers. Only 2-5% is actual semantic content.
Three steps. Zero friction.
Request Arrives
Any visitor hits your URL. Onto's edge middleware inspects the Accept header and User-Agent in under 1ms.
Human browsers send Accept: text/html. AI agents send Accept: text/markdown or use known crawler User-Agents like GPTBot, ClaudeBot, PerplexityBot.
Edge Middleware Routes
Based on the signal, middleware rewrites the request to the right representation — HTML for humans, Markdown for agents.
No network calls for human traffic. Agent requests are rewritten to pre-compiled .onto payloads. Sub-15ms overhead in p99.
Clean Payload Served
AI agents receive compact, semantic Markdown/JSON with preserved hierarchy, tables, code blocks, and metadata.
10-100x smaller payloads. Zero hallucination noise. Accurate prices, descriptions, and documentation every time.
Two paths. One URL.
What Onto extracts
Four components. One system.
AIO Score Calculator
Free public tool. Enter any domain, get an instant AI-readiness report. The entry point to the Onto ecosystem.
@onto/next Extractor
Open-source Next.js plugin. Compiles your routes into clean Markdown at build time. npm install @onto/next.
Edge Middleware
Bot-aware traffic cop at the CDN edge. Routes AI agents to .onto payloads, humans to HTML. Sub-15ms overhead.
Control Plane (Pro)
SaaS dashboard for analytics, hidden prompts, and policy management. See which AI agents crawl your site and control what they see.
See it in action
Scan any website and see exactly what AI agents currently receive — and what they could get with Onto.