Skip to main content
POST
Verify Document Truth
The current implementation simulates extraction and AI verification. Its generated verdict and confidence are not evidence of document authenticity. Do not use this endpoint to approve identities, establish compliance, or authenticate documents.
The handler accepts agent_id and document_hash, with optional document_type, file_name, and metadata. The agent must exist and be active. It does not accept document bytes in document_b64, perform OCR, or compare an uploaded file with the supplied hash. The handler creates its record synchronously. Use the returned document identifier with Get Document. Generated extraction hashes describe simulated content, not extracted file bytes. Pipeline receipt signatures currently contain system markers rather than cryptographic signatures. For cryptographic record verification, use Verify Attestation with a real signed attestation and the original payload or document hash. That checks integrity and record status, not whether the document’s factual claims are true.

Authorizations

X-API-Key
string
header
required

API key for machine-to-machine authentication

Body

application/json
agent_id
string<uuid>
required

Requesting agent

document_hash
string
required

SHA-256 hash of the document

document_type
string
file_name
string
metadata
any

Response

Document verification result

verification_id
string<uuid>
document_id
string<uuid>
document_hash
string
status
enum<string>
Available options:
pending,
verified,
failed
results
object[]
verifications
object[]
claims
object[]
created_at
string<date-time>