Laboratory › Developers
Developers
Everything published here has a machine-readable equivalent generated from the same record in the same pass. The pages and the JSON cannot disagree; a build test fails if they do.
Start here
Quickstart
The whole public API in five minutes: fetch a claim, pin an exact version, detect withdrawal, verify a digest.
API overview
What each family is for, and what a response does and does not let you conclude.
Reference
Every endpoint, generated from the registry the build emits routes from.
Examples
Copyable cURL, JavaScript and Python against endpoints that genuinely exist.
What exists today
| Family | State | Auth | Fixtures | Carries scientific authority |
|---|---|---|---|---|
| Scientific records Published scientific claims and the record of how their standing has changed. Empty by design today: nothing has completed the release process. |
Available | none | excluded | No — it transports records, it does not qualify them |
| Reference documents The vocabulary, the publication rules, the schemas, the operational status and the ledger of what was deliberately not built. |
Available | none | excluded | No — it transports records, it does not qualify them |
| Demonstration fixtures The worked fixture claim and everything attached to it. Not science. |
Available | none | fixtures only | No — it transports records, it does not qualify them |
| Integrity and crawler documents The build manifest and the crawler-facing documents. |
Available | none | excluded | No — it transports records, it does not qualify them |
| Resources and capabilities Typed records for everything Tiffany offers or will offer, the capabilities they enable, and the published architecture. |
Available | none | excluded | No — it transports records, it does not qualify them |
What does not exist, and why
A polished page that truthfully says not yet available is worth more than infrastructure built to make a portal look complete. Each of these was designed and then deliberately not built, with the condition that would change the answer:
| Capability | State | Build it when |
|---|---|---|
| Research, evidence, module, dataset and release endpoints | Planned | The first finding, module or dataset clears release review. |
| Authentication | Not yet available | A non-public tier exists, or a write path exists. |
| API keys | Not yet available | Authentication activates. |
| Rate limits | Not yet available | A request-time computed endpoint exists, or abuse makes anonymous access unworkable. |
| Webhooks | Planned | A consumer needs latency below the polling interval, or polling load becomes material. |
| SDKs | Not yet available | Authentication, pagination or request signing makes a correct client non-trivial to write by hand. |
| Interactive playground | Deferred | Authentication exists and constructing a correct request by hand becomes genuinely hard. |
| Developer accounts and organisations | Deferred | Credentials exist and more than one party needs to manage them. |
| General graph query | Deferred | An external replicator needs a question the bounded set cannot express, twice. |
Build and verify
Verification
Re-derive a record digest, check an artifact, check the whole site against one manifest — and the six different things "verified" can mean, which this laboratory keeps apart.Schemas
15 published JSON Schemas. Every emitted document is validated against its schema during the build, so these are enforced, not decorative.OpenAPI 3.1
Generated from the same registry the routes come from, and tested against the real route inventory in both directions.Machine clients and agents
The rules an autonomous client must follow, including when it is required to stop.
Operations
API status · Contract changelog · Versioning policy · Errors · Security · Use policy
There is no support address, no contact form and no newsletter. The channel for disputing a claim is a challenge contract, which is a structured object rather than a message.
NextAPI overview