Spinning up
Live
+312AI citations this month
Press⌘Kto search
Spinning up
Topic · GEO and AI visibility
The OpenAPI of agentic browsing.
Definition
agent.json is a proposed manifest at the site root that declares an AI agent contract for the website: supported tasks, endpoints, authentication, and content fetching paths. It pairs with the MCP (Model Context Protocol) standard to make a website fully agent-readable.
Services that operate this topic
Service
Custom AI workflows that eliminate manual reporting, route leads instantly, and keep your CRM clean. so your team can focus on closing.
Service
Optimize your brand to appear in AI-generated recommendations across ChatGPT, Gemini, Perplexity, and Google AI Overviews.
Industries that care about this
Vertical
B2B SaaS
B2B SaaS in 2026 buys through ChatGPT and Perplexity before it ever sees Google. If your brand isn't cited in AI answers, demos don't book.
Vertical
AI-native companies
AI-native companies need GEO that names the model, the use case, and the developer adoption signal. Generic positioning loses to specific technical-buyer hooks.
FAQ
It is an emerging convention rather than a ratified W3C standard. Several vendors are converging on the format. Adoption is highest among AI-native and developer-tool brands.
Site identity, supported task types, content fetching endpoints (often /api/agent/*), authentication, MCP server location, rate limits, and a permissive license declaration.
Not directly. It affects AI agent discoverability, which is a separate channel. Treat it as part of the GEO stack, not the SEO stack.
agent.json declares the contract; an MCP server implements the methods. A site can have one without the other, but the pair gives full coverage.
If the site has structured content (products, services, locations, knowledge base), yes. If it is purely brochure-ware with no machine-readable data, the value is lower.
Talk to the team