A Treeship receipt is the same bytes wherever it was produced. An agent running under any harness below verifies against the same trust roots as an agent running under any other, with no registry in the loop. Every card says where the integration actually stands, in one word, with the release beside it.
One skill file teaches every agent the same four commands. Where the harness exposes hooks, a plugin signs outside the model's context, so the record does not depend on the model choosing to keep it.
The official plugin hooks SessionStart, PostToolUse and SessionEnd, so every session becomes a sealed package without the model being asked. Skill and MCP bridge for the lighter tiers.
Skill and MCP bridge shipped. The plugin is a skill bundle awaiting marketplace listing; Codex exposes no pre/post tool-call hooks yet, so there is no bypass-proof tier to ship.
Signed receipts for tool calls through the MCP bridge, plus wrap-friendly shell hooks. A hook-tier plugin would need a VS Code extension intercepting Cursor's tool events, which Cursor does not expose.
The gateway plugin captures before_tool_call and after_tool_call in the gateway process, pairing every intent with its result. Skill file and MCP bridge for the lighter tiers.
Skill and MCP bridge shipped; the actor is set by TREESHIP_ACTOR so receipts name the agent rather than the bridge. The hook plugin (PreToolUse, PostToolUse) is verified end to end and awaits listing.
Skill file and MCP bridge. Hermes has not confirmed a gateway hook surface, so skill plus MCP is the ceiling until it does; the page says so rather than implying more.
The first host for agent-to-agent verification: the packaged skill mints the nonce, verifies the other agent's presentation, refuses on any failure and records the verify. Approvals are blocked because the decision lives only in Grok's UI.
Perplexity is shipping the official Treeship Computer skill; receipts name the agent perplexity-computer. Pro Search has first-party connectors only, so nothing ships there.
Drop-in packages for the two protocols agents already use to reach tools and each other. Both sign with the ship's key; neither changes the wire format.
A drop-in MCP client. Every tool call gets an intent receipt before dispatch and a result receipt after; approval-gated calls are bound to their grant. Signing failures are reported, and TREESHIP_STRICT=1 fails the call instead of proceeding unrecorded.
Task intents and results attested on both sides. Since 0.27 the receiver refuses foreign work until the sender proves live key control against a nonce it minted, and the hand-off records that verify as custody: live.
For code that calls tools directly rather than through a protocol: a mixin, a wrapper, or a client library that signs on the way through.
Receipts for every tool call on all three of the reference's runtimes, single-use merchant approvals, the checkout hand-off and the host's order, and a Claude Code plugin that wires it. Refusals are signed, not missing.
Receipts for every chain and tool call through a callback handler, chained from the session root.
Wrap any PortableTool and every call gets an Ed25519-signed receipt in a tamper-evident, offline-verifiable chain. A Rust crate for Rust agents.
Attest actions, approvals and hand-offs, add timeline events, close sessions, verify. Bootstraps the matching CLI on first use and warns when the CLI is on another release line.
The same surface for Node and edge runtimes, with verification through the WASM core instead of a subprocess, so there is no binary on PATH to substitute.
The Rust verifier compiled to WebAssembly: check a receipt, a chain or a package in a browser, a worker or a serverless function, against your own trust roots, with no network.
Payment networks are deciding how an agent may pay. Treeship is the record of what the agent did on the way. One standard carries a Treeship attestation inside its credential; the others sit beside it.
An independent implementation of the v0.1 draft: treeship vi mints the agent's key, checks a purchase against the mandate, signs the Layer 3 pair for the network and the merchant, and carries a Treeship receipt in the spec's own agent_attestation claim. Interop with the reference SDK is tested both ways in CI.
Complementary, not integrated. They sign agent identity and payment authority at the merchant's edge and on the network; Treeship signs the agent's steps, the merchant's approvals and the cart, offline. A deployment can run both.
Treeship is one of several Zerker Labs systems. The others emit or consume the same evidence, so a policy decision and the action it authorised verify together.
A Reason action-authorization certificate signed and chained as a Treeship receipt under a registered predicate, so the policy decision behind a purchase or a price change verifies independently of the engine that made it.
The gateway that routes, observes and meters agent traffic. Treeship is the proof layer it points at for who can prove what happened.
Treeship as the portable proof layer for what an agent remembered and when: a memory write is an attested action, a recall a verifiable read.
Products that carry Treeship receipts for their own users. Status is the partner's, stated as it is.
Lobster handles the wallet and settlement; Treeship proves what happened. Every payment attested through treeship wrap, with a published commerce template.
Local receipts, approval binding for order placement and audit trails for agents on Robinhood's trading MCP. A receipt template ships; Robinhood's own rollout is gradual and theirs.
Ninja Dev locally today; SuperNinja's remote VMs through MCP and GitHub once invitations and rooms land on their side.
Any agent that reads a skill file can produce a receipt today. A hook-tier plugin needs a runtime that exposes pre- and post-tool-call hooks; where one does, a plugin is about a day of work against the OpenClaw one.
npx skills add zerkerlabs/treeship --skill treeship --agent <name> -g -y
How the skill works ↗