Agent ready is a marketing phrase with no agreed definition, and at least one large vendor markets it as product language. The checkable version is four questions: is there an MCP server or a documented API, did the vendor build it, how does it authenticate, and can one person get access without a procurement cycle.
This site does not use agent ready as a rating, because a rating nobody can reproduce is an opinion. It publishes the inputs instead, and lets you decide what threshold you care about.
An impressive number of tools describe themselves as built for agents while shipping nothing an external agent can call. The two claims live in different places: one on the homepage, one in the developer docs. The directory records the second and cites it.
The reverse trap is real too. A tool with no MCP server and a clean, documented REST API is often more usable to an agent than a tool with a thin server and no docs. 263 of 293 entries have no documentation URL recorded at all, which is its own signal.
Agent ready is in active commercial use as product language by at least one large data vendor, so it is not neutral ground. The term used throughout this site is agent reachable, and it means exactly one thing: a server was found, on a stated date, and who built it is recorded.
Every number on this page is generated from directory.json at build time and carries the date it was baked: 2026-08-25. Nothing is typed by hand, nothing is rounded, and nothing is estimated. The underlying data is published in full. Where the honest answer is a zero, the zero is printed.