Enterprise - by agreement
The archive itself
For platforms, investigators and compliance teams that need the record as infrastructure rather than page by page: the current record database, the documents corpus with every file hashed at capture, bulk history, and service levels in writing.
What an agreement covers
| The record | The full current database - every launch, its birth artifacts by hash, coverage windows, and the corrections register inside the file. The schema is public, column by column. |
| The documents corpus | Every launch document we hold, hashed at capture and dated to the second - including files whose hosts no longer serve them. It is what connects operations whose funding never converges: in one measured case, twelve wallets financed through fifty pass-through wallets, no two chains meeting, were linked by five byte-identical documents. Money can be routed apart. The files a brand is made of get reused, because relaunching it fast means reusing them. |
| The feed | Token creations as we record them, for pipelines that cannot wait for the record cycle. Scoped per agreement. |
| Custody | Build fingerprints are published and snapshots are held off-site; custodian declarations for records used as evidence are available under agreement. |
See the data itself
The record's full schema, column by column with sample rows - the live documentation page, embedded here:
Listing diligence, on the record
Every launch we cover carries the same documented check - the same thresholds, published in Method, applied identically to every token and every customer. The result is a fact about the record ("checked, no markers found" / "findings on record"), never a judgment about a team. Your diligence file cites our record; the method and the corrections register stand behind it.
Why this and not Pro
Pro unlocks the pages for a person. An agreement hands your systems the data those pages are rendered from - the whole record as a file, the documents corpus by hash, and the feed - with terms, service levels and custody in writing. If your team asks "can we get this into our pipeline", you are an Enterprise conversation.
Invoiced, under a signed agreement, with a named contact. No checkout: this is a conversation.
Useful in a first email: what you would put the record behind, the venues and window you need, and whether records will be cited as evidence (that decides the custody terms). hello@chainoftitle.org