One command turns your repo and coding-agent history into a verified passport your client can re-run themselves. Built for teams shipping AI-assisted work.
On a phone right now? Star the repo and it waits in your GitHub account.
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.
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.
One passport, four doors. Each one below is shown as the thing it actually is, because a verification product should never ask you to imagine it.
Under it all, one CLI: Claude Code first with Cursor and Codex in beta, executed checks for Node, TypeScript and Python (beta) projects, and a compliance export pack (EU AI Act provenance, CycloneDX AIBOM, procurement answers) generated from the same passport.
A verification product should be verifiable. Mantyl ships every release under its own passport, five checks independently reproduced, and every claim below links to something you can check yourself, right now, without an account.
A free passport is your evidence, honestly labelled. Mantyl Verified removes the last doubt: neutral infrastructure re-executes every recorded check from scratch and signs the result, the way a buyer trusts a surveyor over the builder. The outcome is a clean sign-off: the delivery is accepted on evidence, not assurances, and the final invoice has nothing left to argue about.
Self-attested says trust me. Independently attested says check for yourself. The mark is revoked if the evidence behind it can’t be reproduced.
No subscription. No seats. Pay when a delivery needs an independent signature, nothing when it doesn’t. Less than an hour of your rate, billable to the project.
Free forever. No account, no credit card.
£0 FOREVER
When the handover needs independent proof.
£29 ONE-TIME · PER PROJECT
14-day no-questions money-back guarantee
No paywall stands between you and a finished handover, and passport.json stays open so the ecosystem can build on the format. Full terms 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, and the CLI's source is public so you never have to take it on faith.
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: scanning, executed checks, passport generation, publishing to a shareable link (free while Mantyl is in alpha) and the compliance export pack all cost nothing. Mantyl Verified is the one paid thing: £29, one-time, per project, buys an independent re-execution of your recorded checks on neutral infrastructure and a signed accreditation on the passport. Every purchase carries a 14-day no-questions money-back guarantee, and there is no subscription, ever, until Agency arrives.
Yes, and that changes what a passport is: one workflow step (or npx mantyl ci anywhere) executes the checks in the runner's Docker and regenerates the passport on every push, so the evidence accumulates for the life of the project instead of proving one moment. Exit codes gate the job honestly: 4 when checks fail, 5 when no sandbox exists, and skipped never masquerades as passed. At handover points the passport can be sealed as a DSSE attestation, the same format GitHub's own artifact attestations use, and your README badge dates its evidence so stale proof looks stale. The action and the CI docs are at mantyl.dev/docs/ci.
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.
The CLI is, fully. Everything that runs on your machine, including the secret redaction, the sandbox and the session-store adapters, is MIT licensed at github.com/jopli11/mantyl-cli, so you can audit exactly what a tool reading your private transcripts actually does. The hosted passport service and the Mantyl Verified signing infrastructure stay server-side, which is precisely what makes an independent signature worth something: it comes from a key nobody's laptop holds.
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.
Agents: Claude Code first, with Cursor and OpenAI Codex support 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. Stacks: Node and TypeScript projects get the full executed-check treatment, and Python joined in beta with 0.6.0 (uv, poetry, pipenv or pip installs, then pytest, ruff and mypy when your project declares them). Narrow integrations produce deep output, and more of each follow as they reach 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