Initiates the verification process for a truth claim. You can choose from multiple verification methods depending on the required assurance level and speed. The claim transitions fromDocumentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
pending to verifying and a verification job is queued.
Verification results are delivered asynchronously. Poll the Get Truth Claim endpoint or subscribe to the truth_claim.verified webhook event to receive results.
Authentication
RequiresX-API-Key header or Bearer JWT token. Tenant-scoped via X-Tenant-ID.
Path Parameters
The unique identifier of the truth claim to verify. Format:
maip-tc:ULID.Request Body
The method to use for verification. One of: -
witness — multi-agent witness
consensus (fastest, fully automated) - ai — AI-powered analysis using
document understanding and anomaly detection - human — routes to a human
reviewer for manual assessment (highest assurance)Processing priority for the verification job. One of: -
normal — standard
queue priority - high — expedited processing, prioritized in the
verification queueResponse
The truth claim identifier.
Updated status. Transitions to
verifying upon successful submission.Unique identifier for the verification job. Use this to correlate webhook
events.
The method being used for verification.
ISO 8601 estimated completion timestamp. Accuracy varies by method:
witness
(minutes), ai (minutes to hours), human (hours to days).Verification Methods
| Method | Assurance | Speed | Description |
|---|---|---|---|
witness | Medium | Minutes | Multi-agent quorum votes on claim validity |
ai | Medium-High | Minutes-Hours | AI models analyze evidence and detect anomalies |
human | Highest | Hours-Days | Human expert reviews claim and evidence |
You can trigger multiple verification methods for the same claim to achieve
layered assurance. Each method runs independently and results are aggregated.

