Document360 has published the kind of list every documentation vendor eventually writes, and it is more useful than most. In Top 7 API Documentation Tools: Key Features, Pros & Cons, the knowledge base company reviews itself alongside Swagger, Redoc, Stoplight, ReadMe, Mintlify and GitBook, and names Docusaurus and Postman as others in the field. The framing is right for 2026: documentation tools “are no longer just a static reference generator,” and the questions have changed from “is it interactive?” to “Is our content being surfaced to AI agents?” The page itself opens with an offer to score whether “your documentation [is] AI-agent ready.”
There are no market figures beyond one attributed claim, that documentation “is one of the top four things that companies consider when deciding to integrate with a third-party API,” from a 2025 report. It is a vendor ranking that includes the vendor, and it should be read that way. What survives is the evaluation method, which any team choosing a tool could reuse: spec import time, reference accuracy, interactive consoles, code samples and publishing workflows. The post is also honest that the dream of docs generated entirely from code does not survive contact with reality: “you will need some manual writing, so think hard about the editing options available.” In its own feature row, Document360 lists an AI writing agent, AI search and an MCP server.
The catalog holds Document360 as a provider in its own right. The Document360 provider page lists 6 API pages, including the Document360 Articles API and Document360 Categories API that hold the content its docs portals publish, and the Document360 Project Versions API for versioned docs. The agentic access profile maps 15 operations, 6 of them acting. Spec presence, agentic access, auth clarity and the rate limit signal are lit on the Agent Readiness score.
The Kin Score is 37.0, thin band, with contract quality at 63.3 and discoverability at 57.1 against operational transparency at 10.5 and contract governance at 9.8. The Agent Readiness score is 17.9, agent-aware. The MCP server dimension is unlit, though the post lists one among Document360’s own features, and so are agent skills and error semantics. Either the catalog has not found the server or it has not been published where a probe would look, and that is worth checking on our side. A company that offers to score whether your documentation is agent-ready is a natural candidate to be scored the same way. On this record, the documentation vendor’s own agent layer is the thinnest part of its listing.