Per-document support diagnostics (visibility, failures, history).
Answer three support facets for ONE document that no other surface exposes (BACKE-3528 / ADM-23): (1) visibility_reason - are this document’s vectors present in MVS (searchable) and, if not, why (the ADM-01 unsearchable class, made per-document answerable via the ADM-02 vector-presence machinery); (2) recent_failures - the source object’s own status/error, with an honest note that structured batch errors are aggregate-only; (3) diagnostic_history - the document’s processing history from its own _internal records. Every facet returns a real value, or an empty/None value with a reason naming what would carry it.
Authorizations
Mixpeek API key, sent as Authorization: Bearer mxp_sk_.... Create one in Studio under Settings → API Keys, or with an admin key via POST /v1/organizations/users/{user_email}/api-keys. A missing header returns 403; an invalid or revoked key returns 401.
Namespace id (ns_...), not the namespace name. This scopes the request rather than authenticating it, and it is required on every operation marked x-mixpeek-namespace-scoped.
Path Parameters
The ID or name of the collection.
The ID of the document.
Response
Successful Response
Support diagnostics for one document (BACKE-3528 / ADM-23).
Whether this document's vectors are present in MVS, and why.
The source object's failure history, with an honest coverage note.
The document's safe processing history.
The document's originating bucket object id (lineage root).

