Mantyl compiles your repository, your coding-agent history and executed checks into a verified project passport, a handover document your client can independently re-run.
On the left, what the recipient of an agentic build gets today: a repository, a README the agent wrote, and optimism. On the right, the same project delivered with a passport.
The code runs. The story of how and why it runs left with the closed context window, and the client finds out slowly.
The recipient re-runs the checks on their own machine before accepting. Both sides know exactly what changed hands.
Four stages in the order you already work. Nothing changes until the end of the project, and the end becomes evidence.
Your agents, your repo, your pace. Mantyl reads Claude Code, Cursor and Codex history where it already lives, so the project needs no ceremony while it’s being made.
mantyl verify executes install, build and tests in a Docker sandbox. Then every claim is labelled with what the evidence supports, never blended.
mantyl generate compiles the passport and you approve every line before it goes anywhere. Publishing to a shareable link is one command and your choice.
Your client runs mantyl receive and reproduces the checks on their own machine. Divergence is named by file. Agreement ends in exit 0.
Narrow integrations, deep output: Claude Code and TypeScript first, with Cursor and Codex in beta. The eight-status truth model behind the labels is documented in the truth model.
Architecture, setup, decisions, risks, unfinished work and verification results. Every claim is labelled with its source, every section linked to evidence, ending in acceptance rather than optimism.
Verified, repository-backed and agent-only claims are kept apart, and unknowns are findings, not footnotes. Visible uncertainty is safer than manufactured confidence.
Environment, dependencies and run steps verified from a clean machine, not copied from a README that was true three weeks ago.
Key decisions and abandoned approaches recovered from your agent sessions and recorded with dates and links before they vanish.
The recipient acknowledges what was delivered, verified and left outstanding. You keep a defensible record of the transfer.
Read a real one first: the passport Mantyl generated for itself, live and hosted. Then the annotated example for booking-app with all eight sections, including the check that failed.
Start with mantyl doctor: it tells you honestly what your first passport will contain. Without Docker you still get facts, claims and recovered decisions. With Docker Desktop running, the passport carries executed proof, which is the point of the document.
Skipped checks are recorded as skipped, never passed. A thinner passport that tells the truth beats a thicker one that guesses.
A house buyer doesn’t take the builder’s word for it, they pay a surveyor for independent assurance. Mantyl holds that position for software: the verification layer between an AI-built project and its next owner.
Documentation is not the product. Trust is. The mark is revoked if the evidence behind it can’t be reproduced.
The CLI is free forever, hosted passports are free while Mantyl is in alpha, and Mantyl Verified is a one-off credit per project at the moment a delivery needs independent proof. Agency comes later: £99 a month for a hundred verifications, once one-off credits have earned it.
Free. Forever. No account.
£0 FOREVER
Free while in alpha
£0 DURING ALPHA
One credit per project
£19–£49 PER PROJECT, BY SIZE
No paywall stands between you and a finished handover, and passport.json stays open so the ecosystem can build on the format. Every tier is spelled out in full on the pricing page.
Raw code and transcripts are processed locally by default, behind fail-closed secret redaction. Nothing needs to leave your machine to get a passport.
No usage tracking, no crash reporting, no analytics in the tool itself. That is a product promise, not a settings default.
The owner decides what a recipient sees. Sensitive history and wrong inferences never go out blindly.
No magic quality scores and no hidden failures. We never tidy a passport to make it look healthier. Visible uncertainty is the product working.
Documentation describes software. Agent memory continues it. Observability explains it.Mantyl transfers responsibility for it.
Documentation describes software; Mantyl transfers responsibility for it. The difference is provenance and verification. Every claim is labelled as agent reported, repository confirmed or verified by execution, checks actually run in a sandbox, and the recipient can independently recheck everything with one command. Documentation that merely repeats what an agent said is exactly the problem.
A prompt produces prose from one session's memory. Mantyl ingests history across sessions, inspects the repository directly, runs deterministic checks, detects contradictions between what was said and what exists, and records the decisions that shaped the project. The value is the evidence chain, not the text.
The CLI is free forever with no account, and hosted passports are free while Mantyl is in alpha. Mantyl Verified is the paid layer: a one-off credit per project (£19 to £49 by project size) buys an independent re-execution of your recorded checks on clean infrastructure and a signed accreditation on the passport. Credits are refundable until the verification runs, and there is no subscription until Agency arrives.
Nothing, unless you publish. The CLI is local first: scanning, verification and reports all happen where the project lives, and transcripts pass through fail-closed secret redaction before anything is stored. Publishing uploads the passport document you approved and nothing else, never your source code.
Then the free CLI already covers you. Generate a passport at each delivery, publish it if the client wants a link, and pay nothing. When a delivery deserves independent proof, one Verified credit covers that one project, which is exactly how often handovers actually happen. No subscription to justify.
Claude Code and TypeScript projects first, with Cursor and OpenAI Codex support now in beta: Mantyl reads their local session stores the same way, with the same redaction, so claims and decisions flow from any of the three. Narrow integrations produce deep output, and more agents follow as each one reaches the same standard.
The CLI is free and local first. There is no account and nothing leaves your machine unless you say so. Install it, run it on a real project, and the next delivery you make carries proof instead of promises.
Free CLI · No account · Local first · MIT licence