Skip to main content
POST
Verify Truth Claim
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 from 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

Requires X-API-Key header or Bearer JWT token. Tenant-scoped via X-Tenant-ID.

Path Parameters

string
required
The unique identifier of the truth claim to verify. Format: maip-tc:ULID.

Request Body

string
required
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)
string
default:"normal"
Processing priority for the verification job. One of: - normal — standard queue priority - high — expedited processing, prioritized in the verification queue

Response

string
The truth claim identifier.
string
Updated status. Transitions to verifying upon successful submission.
string
Unique identifier for the verification job. Use this to correlate webhook events.
string
The method being used for verification.
string
ISO 8601 estimated completion timestamp. Accuracy varies by method: witness (minutes), ai (minutes to hours), human (hours to days).

Verification Methods

You can trigger multiple verification methods for the same claim to achieve layered assurance. Each method runs independently and results are aggregated.

Authorizations

X-API-Key
string
header
required

API key for machine-to-machine authentication

Body

application/json
claim_id
string<uuid>
required

Claim to verify

Response

Verification result

valid
boolean
verification_result
object
receipt
object