Frequently Asked Questions
What does 'agent-ready' mean?
An agent-ready site means an AI agent (ChatGPT, Claude, Cursor, Perplexity, etc.) can discover it, read content in machine-readable format, understand access policies, and interact with APIs when needed. The more open standards your site supports, the higher its readiness.
Why do I need this if I don't work with AI?
AI agents already answer questions about your product, cite your site, and sometimes make purchases. If your site isn't agent-ready, agents may either ignore you or give users inaccurate information. In 1–2 years, this will be as basic as mobile-friendly is today.
Where do the checks come from?
All checks are based on open standards: RFCs (8288, 9309, 9727), specs from modelcontextprotocol.io, agentskills.io, llmstxt.org, contentsignals.org, aiia.dev, and others. Full spec links are in each check card.
Is this free?
Yes, scanning and viewing results is completely free. Prompts, instructions, and check details are public too. We ask for an email only if you want to discuss turnkey implementation — that's a paid offering.
Is it safe to give you a URL?
Yes. We make only GET requests to your site's public endpoints (like any search bot). We don't request private data. URLs aren't stored without your consent. The full audit log is available in each check card.
How often are checks updated?
Standards emerge and evolve constantly. We add new checks 1–2 times per quarter.
Can I scan a password-protected site / staging?
Currently the scanner works only with publicly accessible URLs. Support for HTTP Basic Auth and API keys is on our roadmap.
What does each standard mean?
Full description of each standard is in the corresponding check card. Also see the glossary for detailed articles on each term.
How is this different from isitagentready.com?
Our core UX is close to isitagentready by design — it's a working pattern. Differences: (1) RU/EN localization; (2) unique checks: llms.txt, Schema.org JSON-LD, ai-agent.json (Aiia, March 2026), RateLimit headers; (3) turnkey implementation; (4) future niche benchmarks.
What is GEO and how does it relate to agent-readiness?
GEO (Generative Engine Optimization) is content optimization that makes AI assistants (ChatGPT, Perplexity, Gemini) cite your site in their answers. Many agent-readiness technical standards (Schema.org, llms.txt, robots.txt AI-rules, ai-agent.json) are also the technical foundation of GEO. In our scanner, 10 of 23 checks are GEO-relevant.
Why is there no Commerce category in the Russian version?
Agentic commerce standards (x402, MPP, UCP, ACP) are built around international payment rails. Russian alternatives don't exist yet. The Commerce category is visible in EN. We'll add Russian-specific equivalents once they emerge.