Manifest Ships Autofix to Silently Repair Broken AI Agent API Calls
Manifest's open-source LLM gateway ships Autofix, a self-healing layer that patches and replays broken provider requests before your agent ever sees the error.
PRO- Autofix is live: Manifest's open-source LLM gateway now patches and replays broken provider requests (
400/404/422) automatically, before your agent sees the error. - No setup needed: Autofix is on by default for all Manifest Cloud accounts, including the free plan — nothing to configure.
- Manifest deprecated its own LLM router: After 4 months and 7,000 cloud users, the team concluded smart routing adds unpredictability and rarely saves money vs. caching.
- 300+ models, 32 providers: The open-source gateway supports OpenAI, Anthropic, Google, xAI, Groq, Ollama, and more via one OpenAI-compatible endpoint.
- Self-host or cloud: MIT-licensed, 7.4k GitHub stars, 95k+ Docker pulls; one-click deploys on Railway, Render, AWS, GCP, and DigitalOcean.
- Observability rebuilt: The dashboard now tracks success rate, recovered requests, and shows exactly which field Autofix rewrote per request.
Manifest, the open-source LLM gateway for AI agents, just shipped Autofix , a self-healing feature that intercepts failed provider calls, patches the broken request, and replays it automatically. No code changes, no restarts. It's live for every Manifest Cloud account, free plan included.
The silent killer of agentic workflows
Anyone who has run a long-running agent in production has hit this: a provider silently renames a parameter, your agent sends the old name, gets a 400 back, and dies mid-run. You find out in the morning. The fix is a one-line rename you had no way of anticipating.
According to Manifest, citing Datadog's State of AI Engineering report, 5% of LLM API calls fail in production, and most of those errors are avoidable. Deprecated model names, unsupported parameter values, malformed tool schemas , these are all fixable at the gateway layer, before the error ever propagates up to your application.
How Autofix actually works
Autofix sits in front of Manifest's existing fallback chain. When a provider returns a repairable error, the flow is:
- The provider returns a
400,404, or422, errors that indicate the request was wrong, not the provider. - Manifest normalizes the error into a structured message and sends both the failed request body and the error to a hosted healing service.
- The healing service returns a corrected request body (for example, renaming
max_tokenstomax_output_tokens). - Manifest sends the patched request exactly once. If it fails again, the original error is returned and the normal fallback chain kicks in.
This story is for Pro members
You've reached the end of the free preview. Upgrade to AlphaSignal Pro to read the full article - and everything else behind the paywall.
Comments
