API reference · Private inference
One verdict, with its evidence
GET/api/attestations/{digest}No key
The verdict a private answer named in x-antimatter-attestation, with the evidence it was reached on: the attestation document, AMD's VCEK for the chip, the release and its Sigstore bundle, and the TLS certificate the router presented. Enough to check it again anywhere; /private does it in the browser. A 404 while the operator has not turned private inference on.
Parameters
| Field | Type | What it is |
|---|---|---|
| digest (path)required | string |
Answer 200
The verdict and its evidence
| Field | Type | What it is |
|---|---|---|
| object | string | One of "attestation". |
| digest | string or null | SHA-256 of the attestation document's format and body: the value private answers carry in x-antimatter-attestation. |
| provider | string | |
| host | string | |
| verdict | string | One of "verified", "failed". |
| current | boolean | A verified verdict whose expiry is ahead. |
| measurement | string or null | The launch measurement the hardware signed, hex. |
| report_digest | string or null | |
| tls_key_fingerprint | string or null | SHA-256 of the TLS key the report binds; requests are pinned to it. |
| hpke_key | string or null | |
| repo | string or null | |
| release_tag | string or null | |
| release_digest | string or null | |
| links | array of object | |
| links[] | string | One of "hardware", "vendor", "code", "log", "tls". |
| links[] | boolean | |
| links[] | array of object | |
| links[] | string | A stable check name, such as report.signature or tls.key. |
| links[] | boolean | |
| links[] | string | The value checked, or what was wrong. |
| enclaves | object or null | What the attested router reports about the model enclaves behind it, in its own words. |
| error | string or null | |
| first_verified_at | string or null | |
| checked_at | string | |
| expires_at | string | |
| evidence | object or null |
Errors
- 404OpenAI shaped error.
- 429OpenAI shaped error.
Every error answers in one shape, with its type, code and the field it names. The whole list is in the docs' Errors section.