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
Prerequisites
- Python 3.10 or higher
Get started
Start with your agent
"Install Manifest in this app: https://dashboard.manifest.build/prompt-python.md"
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
- Create a project in your Manifest dashboard and copy its project key.
- 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.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mnfst-1.1.0.tar.gz | 5.8 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mnfst-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.9 MB
Release files / mnfst-1.1.0.tar.gz
| Download URL | mnfst-1.1.0.tar.gz |
|---|---|
| Size | 5.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a9d14005c2e6f732e869b2216278b17895814d0904b70e7a13a6652e716a463
|
|
BLAKE2b-256 checksum How to use checksums |
28efd9ce3f1a22af8f768773450a9624ebad9f594ec649dcfa42352fc4bcbd98
|
| 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 22, 2026.
Transparency logRelease files / mnfst-1.1.0-py3-none-any.whl
| Download URL | mnfst-1.1.0-py3-none-any.whl |
|---|---|
| Size | 27.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f6f1f7bb5b33886574ea9a9cf7508045147145ca75faa2cc42dad5f0475664a
|
|
BLAKE2b-256 checksum How to use checksums |
f20f63729cbbbe10e92a280a9c1626bbb51d6dc4be1e4575d9e6b17793623846
|
| 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 22, 2026.
Transparency log