API overview

Base URL https://tiffany.systems. Contract version 2026-09-10.

Two rules for reading any response

1. Reaching an endpoint establishes nothing scientific. Availability is not validity. A digest that verifies proves you received the bytes that were published and nothing more. No amount of successful API traffic changes a claim's standing, and no credential ever will either.

2. A status is a vector, not a score. Nine dimensions that routinely disagree with each other. Resolve every term through the ontology rather than matching strings, and do not collapse them into one number — the disagreement is the information you came for.

Transport

tls: TLS only. HSTS is set with a two-year max-age and preload. There is no plaintext endpoint.
methods: GET and HEAD. Nothing on this surface accepts a request body, because nothing on it mutates state.
cors: Access-Control-Allow-Origin: * on every /api path. Everything here is public; there is nothing for a browser origin to be trusted with.
compression: Negotiated by the host.
runtime: Static documents generated at build time. No server-side execution, no database, no request-time computation.

The families

Scientific records Available

Published scientific claims and the record of how their standing has changed. Empty by design today: nothing has completed the release process.

Authority: These endpoints transport records that were already qualified by the publication process. Reaching one of them establishes nothing about a claim. Availability is not validity.

Fixtures never appear in this family. 3 endpoints — see the reference.

Reference documents Available

The vocabulary, the publication rules, the schemas, the operational status and the ledger of what was deliberately not built.

Authority: Definitional. These documents say what terms mean and what rules ran. They contain no scientific claims.

Fixtures never appear in this family. 9 endpoints — see the reference.

Demonstration fixtures Available

The worked fixture claim and everything attached to it. Not science.

Authority: None whatsoever. Every document here carries classification DEMO_FIXTURE and a plain-words notice. A client reading only the scientific endpoints can never receive one of these.

This family contains only fixtures. 7 endpoints — see the reference.

Integrity and crawler documents Available

The build manifest and the crawler-facing documents.

Authority: The manifest establishes which bytes this build produced. It establishes nothing scientific.

Fixtures never appear in this family. 4 endpoints — see the reference.

Resources and capabilities Available

Typed records for everything Tiffany offers or will offer, the capabilities they enable, and the published architecture.

Authority: These describe software and availability. Nothing here carries scientific standing, and a resource being available says nothing about whether any claim is supported.

Fixtures never appear in this family. 4 endpoints — see the reference.

Why the scientific endpoints are empty

No finding has completed archival audit, prior-art comparison, independent replication where the claim requires it, reproducibility packaging, and security, privacy, licence and IP review. Until one does, it does not appear.

This is not a placeholder for a corpus that exists elsewhere and has not been copied over. There is no hidden index. The fixture under /api/demo exists so a client can be written and exercised end to end before the first real record, and it is excluded from every scientific surface.

What a client should do with an empty result

/api/claims.json returning count: 0 is a correct answer, not an outage. The note field says why. A client that treats an empty scientific index as a failure will break on the day the first claim is published, and again on the day one is withdrawn — both are ordinary states.

PreviousDeveloper home

NextQuickstart