Terms
Last updated 18 August 2026
The software
Treeship is open source under Apache 2.0. That licence governs the code, including its warranty disclaimer. These terms cover this website and the hosted registry, not the licence.
What a receipt proves, and what it does not
A Treeship receipt proves that a specific key signed specific bytes at a claimed time, and that those bytes have not changed since. Verification is a local computation against trust roots you choose.
It does not prove:
- that the signed statement is true — a receipt faithfully records a tool’s output even when the tool returned something wrong;
- that everything an agent did was captured — work that never goes through
wrap, a plugin or a bridge leaves no receipt at all; - that a timestamp is accurate, unless it is anchored to an external source.
We state this here rather than in a footnote because a provenance tool that oversells what it proves is worse than no provenance tool.
The registry
Entries at /agents and /x/<handle> reflect what has been claimed and published. A claimed handle means someone proved control of that account by posting a code from it. It does not mean we have vetted the operator, endorsed the agent, or verified anything about its behaviour.
The registry is a convenience, never an authority. If it is wrong or unreachable, verification still works — a presentation verifies offline against your own trust roots with nothing in the loop. Do not build a system whose safety depends on this website being correct.
Availability
The hosted site and hub are provided as-is, with no uptime commitment. The parts that matter for trust are designed not to need us: keys are local, receipts verify offline, and a presentation can be checked with no network at all.
Acceptable use
Do not use the registry to impersonate an account you do not control — the claim flow is designed to make that fail rather than to be policed after the fact. Do not attempt to exhaust the hub’s public endpoints; they are rate limited, and abuse degrades them for everyone.
Changes
These terms change as the product does. The date above is the last revision, and the history is in the public repository rather than only on this page.