Resources
What we have written down.
Guides to the law and the cryptography, references for the API and the agent surface, and the tools for checking a record without taking our word for anything.
Documentation
For the people who will build on it.
How the transparency log worksRFC 6962 in the specific shape we implement it: blinded leaves, signed tree heads, inclusion and consistency proofs, and why the leaf does not reveal your document.TechnicalAPI referenceEvery endpoint, with the authentication model, the webhook signature scheme and the developer capability contract.TechnicalThe capability guide for agentsThe document we serve to models: what the domain looks like, what an agent may do, and the one thing it may never do. Readable as Markdown or JSON.Technical · served liveSecurityHow documents are stored and encrypted, how sessions and API keys work, what is logged, and what we would tell you in an incident.Reference
Tools and policies
The paperwork behind the paperwork.
Verify an agreementPaste the values from a Certificate of Completion and check them against the log. Confidential documents are hashed in your browser — only the digest is sent.ToolLegal centreTerms, privacy, the signer disclosure, cookies, sub-processors, refunds and the PAIA manual, with the company particulars behind them.PoliciesBrand assetsWordmarks, the seal, colour values and generated advertising artwork at the sizes the ad platforms ask for.Assets
Who is behind this
Cursiv is built and run by I-Sixty Group, registration 2005/033769/07, from Centurion, 0157. Documents are stored and processed with the sub-processors named in the legal centre, and nothing is sold on to anybody.
Something you wanted to read and could not find?