Get This Tool
AgentReady
Pricing
- Model
- Free
Summary
Web agents that rely on `web_fetch` hit a wall the moment they encounter a JS-rendered docs site — the content is there, the agent sees nothing. AgentReady exists to close that gap.
The tool indexes public websites — including JS-rendered pages — and exposes the content through a single MCP server your agent connects to once, then queries across 114+ pre-indexed sites or any site you add on the fly. Four MCP tools cover the full workflow: ask a site a question, list what's indexed, submit a new URL, or force a re-crawl. Setup is a one-line MCP config and no API key. The wall you hit is scope: only public sites can be indexed, private documentation behind authentication is out of reach, and the 'Actionable' layer — agents triggering real site actions — is listed as coming later, not live.
Bottom line: AgentReady is the right call when your agent needs cited answers from public documentation sites without building your own crawler — but if your docs live behind a login or you need agents to trigger actions on a site, neither the product's current state nor its self-serve model covers you.
Community Performance Report Card
No community ratings yet. Be the first to rate this tool!
Community Benchmarks Community
Sign in to submit a benchmarkNo community benchmarks yet. Be the first to share a real-world data point.
Pros
Sign in to edit- JS-rendered pages are indexed correctly, so agents get actual content from documentation sites that `web_fetch` returns blank on — no custom rendering pipeline required on your end.
- 114+ sites are pre-indexed and accessible through one MCP connection, which means your agent queries Stripe or Next.js docs with cited answers without you building or maintaining any crawl infrastructure.
- New sites are added in roughly 60 seconds via `submit_site` or the CLI, so when a dependency's docs aren't in the index yet you're not blocked waiting on a support queue.
- No API key or account is required to run a query or grade a site, so evaluation takes minutes rather than a procurement cycle — which matters when you're vetting this mid-sprint.
- Generates a spec-compliant `llms.txt` automatically from a URL paste, so site owners who want their content discoverable by agents don't need to understand the spec or involve a developer.
Cons
Sign in to edit- Only public websites can be indexed — any documentation behind authentication, a VPN, or a private network is out of scope entirely. Teams whose critical docs live in a private Confluence instance or behind SSO have no path forward here and route to a self-hosted RAG stack instead.
- The 'Actionable' layer — agents triggering real site actions like search or transactions — is listed as a future capability, not a shipped feature. Teams building agents that need to do something on a site rather than just read it are building that integration themselves or evaluating tools that already ship it.
- Higher limits, private indexing, and custom deployments are listed as contact-us territory with no published self-serve path. Teams that hit index limits or need dedicated infrastructure mid-project face a sales conversation at the point when they least have time for one.
- There is no self-hosted option. Teams in environments where data cannot leave their infrastructure — regulated industries, enterprise security requirements — cannot use this service regardless of use case fit.
Community Reviews
Sign in to write a reviewNo reviews yet. Be the first to share your experience.
About
- Platforms
- Web, CLI, MCP clients
- API Available
- Yes
- Self-Hosted
- No
- Last Updated
- 2026-07-17T03:29:34.821Z
Best For
Who it's for
- Documentation and support sites
- Developers integrating agents with web content
- Long-tail websites seeking agent compatibility
What it does well
- Enable AI agents to query documentation sites with cited answers
- Index arbitrary public websites for agent access
- Generate llms.txt files for site owners
- Grade existing sites for agent-readiness
Integrations
Discussion Community
Sign in to commentNo discussion yet. Sign in to start the conversation.
Compare AgentReady
Spotted incorrect or missing data? Join our community of contributors.
Sign Up to ContributeCommunity Notes & Tips Community
Sign in to contributeBe the first to contribute. General notes, observations, gotchas, and tips from people who use this tool day-to-day.
Frequently Asked Questions
- Is AgentReady free?
- AgentReady has a permanent free tier alongside paid upgrades. You can keep using a baseline version indefinitely without paying.
- Is AgentReady open source?
- Yes. AgentReady is open source.
- Does AgentReady have an API?
- Yes. AgentReady exposes a developer API. See the official documentation at https://agentready.it.com for details.
- What platforms does AgentReady support?
- AgentReady is available on: Web, CLI, MCP clients.
Hours Saved & ROI Stories Community
Sign in to contributeBe the first to contribute. Concrete time/cost savings, with context. e.g. "Cut my code review backlog from 4h to 45m per week."
Curated lists that include this category
Most agent pipelines treat the open web as a solved problem until they need structured, cited answers from a specific documentation site and discover that raw scraping returns nav soup and JS-rendered pages return nothing. AgentReady indexes public websites — discovering pages via sitemap or link-following — strips the noise, and surfaces content through a hosted `/ask` RAG endpoint and a single MCP server. The core workflow is a URL paste: AgentReady crawls, extracts clean text, generates a spec-compliant `llms.txt` file you can host at your site root, and immediately activates hosted `/ask` and `/mcp` endpoints. No account required to try it.
The differentiating feature is the pre-built index. Rather than asking every team to crawl and embed their own corpus, AgentReady maintains 114+ already-indexed sites — Stripe, Next.js, Supabase, and others — accessible through one MCP connection. Adding a site the index doesn’t already cover takes roughly 60 seconds via the `submit_site` tool or `npx @agentreadyweb/mcp index yourdomain.com`. The vendor states compatibility with Claude, Cursor, VS Code, and any MCP client through a single HTTP endpoint, with a stdio bridge available for Claude Desktop.
For site owners, AgentReady generates a spec-compliant `llms.txt` — the emerging standard for making site content discoverable by AI agents, analogous to `robots.txt` — without requiring a developer. A CLI tool grades any public site’s agent-readiness and supports `ask`, `index`, and `refresh` commands. The comparison the vendor draws is against self-hosted alternatives that require engineering effort and paid services that start at significant monthly costs; AgentReady positions itself as the self-serve option for documentation teams and long-tail sites.
The ‘Actionable’ layer — WebMCP tool definitions that let agents trigger site actions like search, booking, or cart interactions — is listed on the product page as ‘Later’, not live. Integration is via MCP standard, which means any client that speaks MCP works; the vendor lists Claude Code, Claude.ai, and Cursor explicitly, with a full setup guide available per client.