1. Errors that carry the fix
2. A way for agents to give feedback
3. Request logs agents can read
4. Fewer MCP tools
5. Programmatic signup
6. A CLI for complex setup
7. Agent-only endpoints
Read the full blog post: https://t.co/PpF25my1e8
An agent that gets a 400 back doesn't read your docs. It retries.
Your error response is the only line to your agent.
7 ways to make your API agent-ready ๐
Another one we heard a lot: "How is this different from API management?"
Gateways control who gets in. Restless helps whoever's in actually succeed: error recovery, an MCP server, API feedback tools, and self-updating docs.
Met a ton of builders at @AIconference last week. Thanks for sharing what's breaking your APIs!
The #1 question we got: "Does Restless sit in the API layer?"
Nope. It sits next to your API, not in front of it.
Run npx restless init and it reads your real traffic, then builds an API Portal with failed-request logs and fixes.
Next week, we're making our debut at @AIconference. ๐
APIs change. Docs go stale. And more of your callers are agents.
Restless builds an agent portal from live traffic, logs every request, and helps agents recover when things break.
Come see us at booth 128!
Most APIs aren't actually agent-ready.
The endpoint works. The agent still fails.
Agents don't browse your docs. They parse what's there, call what they find, and fail on everything else.
People are building APIs that agents can't call.