AEOAgent Engine Optimization

SEO made websites findable by search engine crawlers. AEO — Agent Engine Optimization — makes services, APIs, and endpoints discoverable by autonomous AI agents. As agents replace browsers as the primary interface between humans and the internet, the services that win will be the ones agents can find, evaluate, and transact with programmatically. AEO is the discipline of optimizing for that surface. This paper defines AEO, explains why it matters now, and describes the primitives that make it work.

For 25 years, discovery meant one thing: rank on Google. You wrote content for humans, structured it for Googlebot, and hoped to appear on page one. SEO was the game because the browser was the interface. That era is ending. Autonomous agents don't open browsers. They don't read marketing pages. They consume machine-readable manifests — JSON, OpenAPI specs, capability descriptors, tool registries. They evaluate trust signals programmatically. They transact via protocols like x402, not checkout flows. The question is no longer "Can a human find you on Google?" The question is: "Can an agent discover, evaluate, and pay your endpoint without human intervention?" That's AEO.

Agent Engine Optimization (AEO) is the practice of making digital services discoverable, evaluable, and transactable by autonomous AI agents. Where SEO optimizes for crawlers that index content for human consumption, AEO optimizes for agents that discover capabilities for autonomous execution. The core primitives: → Machine-readable manifests (x402.json, cleared.txt, OpenAPI specs) → Structured capability descriptors (what you do, what it costs, how to pay) → Trust and attestation signals (methodology-backed verification, not self-reported claims) → Protocol-native payment rails (x402/USDC — agents pay endpoints directly) → Discovery indexes (centralized registries agents query before transacting) SEO has sitemaps, robots.txt, and structured data. AEO has manifests, cleared.txt, and attestation badges.

Three forces converge to make AEO inevitable: 1. Agent proliferation. Every major AI lab is shipping agents — systems that plan, act, and transact autonomously. These agents need to discover services the same way browsers discovered websites. But they can't use Google. They need machine-native discovery. 2. Protocol-native payments. x402 and similar protocols let agents pay for API calls with USDC — no checkout flows, no OAuth dances, no human in the loop. When agents can pay, they need to know who to pay and whether to trust them. 3. Trust at machine speed. Agents making thousands of decisions per hour can't read reviews or ask for recommendations. They need attestation — cryptographic or methodology-backed proof that an endpoint does what it claims, charges what it quotes, and delivers what it promises. The window is open. The standards are forming. AEO is the discipline that connects these forces into a coherent practice.

SEO and AEO share a structural logic but differ in every dimension: SEO targets search engine crawlers. AEO targets autonomous agents. SEO optimizes HTML content. AEO optimizes machine-readable manifests. SEO measures rankings and click-through rates. AEO measures discovery rate, trust score, and transaction volume. SEO's trust signals are backlinks and domain authority. AEO's trust signals are attestation badges, methodology scores, and protocol compliance. SEO's conversion is a page visit. AEO's conversion is a programmatic transaction. SEO asks: "Will Google rank me?" AEO asks: "Will an agent pay me?" They're not competing disciplines. They're adjacent layers. You still need SEO for human discovery. You need AEO for agent discovery. The companies that master both own the full surface.

A complete AEO implementation has five layers: Layer 1 — Manifest Publish a machine-readable descriptor at a well-known path. For x402 endpoints, this is /.well-known/x402.json. It declares your capabilities, pricing, and payment methods. This is your robots.txt for agents. Layer 2 — Index Get listed in discovery indexes that agents query. Cleared Index maintains cleared.txt and cleared.json — machine-native feeds agents consume before transacting. Being in the index means agents can find you. Layer 3 — Attestation Earn trust signals agents can verify. Self-reported claims mean nothing to an agent. Methodology-backed attestation — where a third party crawls your manifest, verifies your endpoints, and issues a score — is what agents weight. Layer 4 — Protocol Support agent-native payment protocols. x402 lets agents pay with USDC on-chain. No API keys, no billing dashboards, no invoices. The agent sends money, you deliver the response. Layer 5 — Signal Emit structured signals that agents consume: JSON-LD, capability schemas, uptime guarantees, pricing stability. The richer your signal, the more an agent trusts your endpoint over a competitor's.

Cleared Index is purpose-built AEO infrastructure. Listed (free) — Instant AEO. Paste your origin URL. We crawl your manifest, generate your listing, and add you to cleared.txt and cleared.json. Agents discover you immediately. Dofollow backlink. JSON-LD structured data. Sitemap inclusion. This is the baseline AEO layer every endpoint needs. Cleared ($149/mo) — Attested AEO. We run methodology-backed checks on your manifest, verify endpoint behavior, and issue an attestation badge. Agents weight attested endpoints higher. Your full catalog is indexed — unlimited SKUs, one operator listing. This is premium AEO. The SDK lets agent developers query the Cleared index before transacting — filtering by attestation tier, category, and trust score. Agents that integrate the SDK only pay endpoints that pass. cleared.txt is the new robots.txt. It's the file agents check before they proceed.

AEO is in its earliest phase — equivalent to SEO circa 1998. The primitives are forming, the standards are emerging, and the early adopters will define the discipline. What comes next: → AEO scoring — quantified agent discoverability metrics, like an agent-native PageRank → AEO audits — automated assessment of your endpoint's agent-readiness → AEO tooling — SDKs, linters, and CI/CD checks for manifest quality → AEO consultancies — the same way SEO agencies emerged, AEO agencies will follow → AEO standards bodies — industry groups defining manifest schemas, attestation protocols, and discovery conventions The companies that invest in AEO now will own the agent discovery layer the same way early SEO adopters owned search. The surface area is new. The window is open. Cleared Index is where it starts.