ReadMe founder Gregory Koberger launches Restless, a toolkit that makes APIs improve themselves from every call, support question and error
Your API is now your product, and it needs to move as fast as you do. Introducing Restless. Every call, support question, pull request, and error message leaves your API better for the next agent.
Context
As AI agents become the main users of many APIs, tools that catch where agents get stuck and fix the API in response could become core developer infrastructure.
Gregory Koberger founded ReadMe, a company that hosts API documentation for developers. Restless is a new product from the same team, and ReadMe's documentation calls it Restless by ReadMe. An API is the interface that lets software, including AI agents, call another company's service.
Deep dive
On October 12, Gregory Koberger posted: Your API is now your product, and it needs to move as fast as you do. Introducing Restless. Every call, support question, pull request, and error message leaves your API better for the next agent.
According to the Restless site, the product draws on real time API logs, answers given by human support staff, feedback from agents and existing documentation from ReadMe, Mintlify, Fern or other tools. It says it catches failed calls and tells the caller how to recover and retry, and that it adds a send_feedback tool to a company's MCP server so an agent can report what tripped it up instead of giving up.
ReadMe's documentation describes Restless as a modern API toolkit to make APIs agent ready. It says Restless runs in an API's request path, captures every API and MCP call, puts the fix right in the error response and gives teams one view of who is calling and what is failing. Setup starts with npx restless init, which installs the Restless SDK.
ReadMe says its customers do not need to migrate anything, can connect existing docs as a source, and get 4,000 extra credits a month. Restless did not publish pricing in the launch post.
What to expect next
Watch whether API companies adopt Restless alongside or instead of documentation tools like ReadMe, Mintlify and Fern, and whether agent feedback through MCP becomes a common pattern.
Also watch how teams handle putting a third party SDK in their request path, and whether Restless publishes data showing that its fixes actually raise the share of successful agent calls, along with the pricing it has not yet published.