Skip to main content

Manifest SDK Architecture

Manifest for Python

Turn 🔴 4xx API errors into 🟢 2xx in real time.

CI PyPI version PyPI downloads

What is Manifest

Manifest is a self-healing layer that fixes and retries failed API requests on the fly.

  • 🎯 Fix failures automatically before they impact your users.
  • 🔔 Get notified of root causes so you can fix them permanently.
  • 🔌 Works across your stack with internal APIs, external services, and agent tools.

How it works

How the SDK works: every call Manifest does not heal is recorded in the background as metadata (method, URL, status, timing, no body); a failure Manifest can heal is sent with its error, patched, and retried once, returning a 200 OK

Every call your app makes is reported to Manifest as metadata only (method, URL without its query string, status and timing), in the background. A failure Manifest can heal is sent in full, so it can be repaired. What is sent.

Prerequisites

Get started

Start with your agent

"Install Manifest in this app: https://dashboard.manifest.build/prompt-python.md"

Read the prompt →

The prompt finds your entry point and stops to let you paste your key.

Start with code

pip install mnfst

Run your app through the CLI, so Manifest loads before the first request:

export MNFST_KEY='your-project-key'
mnfst run uvicorn main:app

mnfst run prefixes any command — mnfst run gunicorn app:app, mnfst run celery -A tasks worker. Or call manifest() yourself, once at startup:

from mnfst import manifest

manifest()  # Once, at startup.
# Keep making your API calls as usual.

Use the source-level call when there is no command to prefix: AWS Lambda, a notebook, or a start command owned by a host dashboard.

Setup

  1. Create a project in your Manifest dashboard and copy its project key.
  2. Set the key as an environment variable:
export MNFST_KEY='your-project-key'

Load the SDK with mnfst run, or call manifest() once at startup, before your first request. Self-healing is enabled by default in your project settings.

Check the install at any time with mnfst doctor.

Try it

Send a request that would normally fail. Manifest catches it, repairs it, and retries:

import httpx
from mnfst import manifest

manifest(on_heal=lambda e: print(f"Healed: {e.heal_status}, Response: {e.replay_status_code}"))

res = httpx.post(
    "https://api.example.com/orders",
    json={"limit": 500},  # Invalid? Manifest fixes it and retries.
)
print(res.status_code)  # See the 200 OK response.

Check your Manifest dashboard to see all repairs and insights.

More

Configuration, limits & development · API contract · Node.js SDK · Website

Metadata

Release files for mnfst 1.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mnfst 1.2.0
File Size Uploaded
mnfst-1.2.0.tar.gz 242.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mnfst 1.2.0
File Interpreter ABI Platform
mnfst-1.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 274.0 kB

Release files / mnfst-1.2.0.tar.gz

Download URL mnfst-1.2.0.tar.gz
Size 242.8 kB
Tags Source
SHA-256 checksum
How to use checksums
7d424462231cdff8f38d35f3f06d88d21e440fe80e6d51d3785b7b70ffd4b324
BLAKE2b-256 checksum
How to use checksums
1e90476ea3823ad1d5b041cdf596816444e1f49d19c97658dd371d0d4fc21c6d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.

Transparency log

Release files / mnfst-1.2.0-py3-none-any.whl

Download URL mnfst-1.2.0-py3-none-any.whl
Size 31.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
53dcfd534800fff5f81bee6b8f27f4c2de2a8379d9d5896ace2abdf2d641efdc
BLAKE2b-256 checksum
How to use checksums
129705bde54442ebcfa1e451d17b90fb4a1624747967d24435bfae06c7813617
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.

Transparency log

Release history Release notifications | RSS feed

1.3.0

2 release files

This release

1.2.0 This release

2 release files

1.1.0

2 release files

1.0.0

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page