Tokenistry documentation
How the Tokenistry stack is put together, how to integrate with it, and where the authoritative description of every endpoint lives.
Start here
API overview
The contract, the conventions that apply to every service, and where to get the specification.
API reference
Every endpoint of every service, browsable, generated from the same documents the services serve.
Integration overview
How a product sits on top of the stack, and which service owns which decision.
Demo console
The operator console against a seeded book. Access is by request.
Where things live
Four places, each with one job, so nothing is documented twice and no two copies can disagree.
| Here | What you will find |
|---|---|
| These documents | Concepts, conventions and integration guidance |
| API reference | Endpoint-level detail, request and response shapes |
| Demo console | The running system, with a book you can explore |
| tokenistry.com | What each module does commercially, and why |
What is not here
Production deployment runbooks, capacity planning, custody integration and chain-specific operational procedure are part of an implementation engagement rather than a public page. They depend on your custody arrangement, your chain and your controls, and a generic version of them would be wrong in the specifics that matter.
If you are evaluating and need that level of detail, start the conversation.