Twelve years ago today, we launched ReadMe. For over a decade, we've powered the UI for tens of thousands of APIs, in the form of documentation.
Agents now make up 72% of traffic to API docs. It's not just how docs are read that's changing. The bigger shift is how APIs are being called and used.
Agents aren't just building integrations on your API; it's how they headlessly access your product. You need to be able to add features without a lifetime commitment, and remove them without eroding trust.
Your API needs to be able to move as fast as you do.
Introducing Restless.
A need for new tools
My favorite thing we've built at ReadMe is hidden in the Analytics tab. It's called Developer Dashboard. You stream your API logs to ReadMe, and two things happen. You can see how your API is actually being used, in aggregate or per user. And your developers can pull up their live API requests without ever leaving your docs.
As APIs have gotten more important, it became clear Developer Dashboard needed to be its own product, and aimed at the agents now calling your API.
ReadMe isn't going anywhere. We're shipping faster than ever, and have a lot launching in the next few weeks. Restless is a new product for a new way of using APIs, and it runs right alongside ReadMe.
Restless makes your API self-improving. Every API call, support question, feature suggestion and error message leaves it better for the next request.
Here's how it works: rather than publishing static documentation, Restless takes what's actually going on via realtime API logs, and pairs it with constantly updating context from all over. Then it makes sure it's right where your user's agents are working, over an MCP server and in your docs, so they know the moment you ship a change.
Agent Recovery
Agents don't like to search for API documentation. They try their best, and give up if they can't find the answer. Restless brings the documentation right to the agent: rather than making it guess, the docs on how to move forward are inserted directly into the API response.
Debugging
When something breaks in production, an agent shouldn't have to guess. Restless gives it direct access to your API's logs, so it can look at what actually happened instead of inventing an explanation. You or your agent can quickly find answers to "which endpoint is throwing the most errors?" or "why did my most recent request break?" Each answer combines live API logs with context about your API.
POST /v1/charges has the highest error rate, 9.3% over the last 24 hours. Most are 500s from a payment provider timeout. Recent failures:
Workbench
Your API is a black box to your users. At the bottom of your docs is the Workbench, which lets them see what's happening on the server and debug on their own. They can filter their logs, see the request and response, and open support tickets if something looks wrong.
Ask a question or dive into the documentation.
Ask anything about this API…
Human Support
Restless answers most questions on its own, but sometimes there's a problem it doesn't know the fix for. Every AI chat can be converted to a human one in a click, so your team can help users get unblocked. And when an agent gets stuck, Restless asks it for feedback, then turns the reply into real fixes, from better documentation to changes in the API itself. The best part: your answers are stripped of any personal data and saved as context, so the more you answer, the smarter Restless gets.
I rotated our API key an hour ago, but calls still return 401 invalid_api_key. What am I missing?
Newly rotated keys usually propagate within a minute. If 401s persist after that, an old key may still be cached in your client.
Your account had two active keys and the SDK was picking the old one. I've revoked it, so retry now and you'll authenticate.
Understand who is using your API
Your API is your product now, so you need to know what your users are actually doing with it. Restless logs every API and MCP request in one place. When a developer hits the same 401 three times, you can reach out before they give up. When someone writes in, you can pull up their exact requests instead of asking them to send logs.
And you don't have to click around a dashboard to do it. Everything is available through the Restless MCP server, so you can help users right from Claude, ChatGPT, Slack, or wherever you already work.
Using with ReadMe
ReadMe and Restless work great together! Restless is the AI-native front door for agents, and you can use ReadMe (or Fern, Mintlify, and others) as the source for context for it.
Every Restless project comes with 1,000 credits a month for free. If you're a ReadMe customer, you'll get 4,000 extra credits a month. Credits cover log ingestion and the dashboard AI, and you can buy more in $100 increments whenever you need them.
If you want to talk more about the future of APIs, I'd love to talk!