---
title: "Manifest Ships Autofix to Silently Repair Broken AI Agent API Calls"
subtitle: "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."
url: "https://alphasignal.ai/news/manifest-ships-autofix-to-silently-repair-broken-ai-agent-api-calls"
author: "AlphaSignal Newsroom"
author_url: "https://alphasignal.ai/editorial-team"
company: "AlphaSignal"
company_url: "https://alphasignal.ai/company/alphasignal"
published: "2026-04-29T15:04:18.000Z"
updated: "2026-08-18T07:00:16.253Z"
type: "Repo"
topics:
  - "Agents"
  - "Infra"
subtopics:
  - "Agent Frameworks"
  - "Model Serving"
  - "Inference Optimization"
upvotes: 16
source_url: "https://github.com/mnfst/manifest"
comments: 0
truncated: true
---

# 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.

[Manifest](https://github.com/mnfst/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:

1. The provider returns a `400`, `404`, or `422` , errors that indicate the _request_ was wrong, not the provider.
2. Manifest normalizes the error into a structured message and sends both the failed request body and the error to a hosted healing service.
3. The healing service returns a corrected request body (for example, renaming `max_tokens` to `max_output_tokens`).
4. Manifest sends the patched request exactly once. If it fails again, the original error is returned and the normal fallback chain kicks in.

_Preview only. Full text requires an AlphaSignal Pro account._

## Sources

- [mnfst/manifest — GitHub](https://github.com/mnfst/manifest)
- [The Open Source LLM Router for AI Agents | Manifest](https://manifest.build)
- [Your failing requests now fix themselves | Manifest Blog](https://manifest.build/blog/auto-fix-release/)
- [Autofix — Manifest Docs](https://manifest.build/docs/autofix/)
- [Everyone is building LLM routers, we deprecated ours | Manifest Blog](https://manifest.build/blog/why-we-deprecated-our-llm-router/)