Writing
Integrations
Treeship inside another system: a harness, a protocol, a product, a standard.
The operator's yes, signed once
In Anthropic's commerce-agents reference, a merchant change applies only after a human approves it. treeship-commerce 0.29.0 makes that click a signed, single-use grant the apply receipt spends exactly once, on all three runtimes, with the console loop unchanged.
Receipts for agentic commerce
Anthropic's Claude Commerce Agents blueprint tells an agent what it may do in a store. Visa, Mastercard and Google are deciding how an agent may pay. Nobody in that stack keeps a record a stranger can check. Checked against a fresh clone.
You can't have agentic commerce without tamper-proof receipts
Anthropic's commerce-agents reference enforces its gates in code and leaves the record to the deployment. treeship-commerce is that record: every tool call signed on all three runtimes, the merchant's approval as a single-use grant, and a receipt for exactly the cart that went to checkout. Verifiable offline, wired by one command.
Robinhood Agentic Trading Needs Receipts
How Treeship can provide local proofs, approvals, and audit trails for agents connected to Robinhood Trading MCP.
Treeship Agent Skills: One Skill, Every Agent
Install Treeship on Kimi Code CLI, Claude Code, Codex, Cursor, OpenClaw, and Hermes. One skill file teaches every agent how to create cryptographically signed trust receipts.
Treeship 0.9: the official Claude Code plugin
Two commands install a plugin whose hooks record every Claude Code session into a sealed receipt. TREESHIP.md tells the agent exactly what is captured.
A2A Makes Agents Interoperable. Treeship Makes That Interoperability Trustworthy.
Google's Agent2Agent protocol gives every agent a way to talk to every other agent. It does not give you a way to verify what any of them actually did. Here is how @treeship/a2a closes that gap, with worked examples you can run end-to-end.
Verifiable Intent: how Treeship becomes the agent's proof of work
Agent attestation in Verifiable Intent credentials: how Treeship proves an agent acted correctly, privately, and within scope.
Every MCP Tool Call Your Agent Makes Right Now Has No Receipt
The Model Context Protocol specification is explicit: tool calls are arbitrary code execution and hosts are responsible for authorization. Most MCP implementations have no answer to this. Here's what closing that gap looks like.
Agent Payments: Lobster.cash + Treeship
Lobster.cash handles wallet and settlement. Treeship proves what happened.
Mastercard Verifiable Intent and Treeship
How Treeship's approval receipts align with Mastercard's open standard for agent commerce.