Restless launches as an API product that fixes itself from real traffic
The ReadMe team launched Restless, which returns fix steps and doc links in error responses when an agent's API call fails, and files a Linear issue or doc update via MCP when the agent is still stuck.
72% OF API DOCS TRAFFIC IS ALREADY AGENTS AND YOUR DOCS STILL ONLY TALK TO HUMANS The team behind @readme just launched Restless, an API that fixes itself from its own traffic. Agent hits your API -> request fails -> the error response itself carries the fix steps and a doc link -> the agent recovers without ever opening your docs. When it still gets stuck, it files feedback through MCP -> that lands as a Linear issue or a doc update. • What @restless_hq ships > Live logs of every request and response, tied to the customer who made it. > A hosted MCP server where agents search and replay their own production calls, with your endpoints and docs exposed as tools. • Why @gkoberger built it > Integrations were written once and deployed, agents call your API on the fly to use your product headlessly. > If a user can do it in your UI, an agent needs to do it through the API, or the human becomes the agent's courier. "Every company is an API company now, whether they want to be or not" -- @sama -> Restless is the first tool that treats your API like the product. Setup is one line, npx restless init, link in the first reply ↓
This post quotes another post: “Restless launches to make APIs improve with every call”