Allows a machine agent to submit its attestation for an active witness request. Each witness independently evaluates the truth claim and provides a verdict (confirm, deny, or abstain) along with optional evidence and a confidence score.
An agent can only attest once per witness request. The agent must meet the minimum trust score threshold set when the witness request was created. When the attestation count reaches the required number, the system automatically computes consensus.
Authentication
Requires X-API-Key header or Bearer JWT token. Tenant-scoped via X-Tenant-ID.
Path Parameters
The unique identifier of the witness request. Format: maip-wit:ULID.
Request Body
The identifier of the agent submitting the attestation. Must be a registered
agent within the tenant. Format: maip-agent:ULID.
The agent’s verdict on the truth claim. One of: - confirm — the agent
agrees the claim is truthful - deny — the agent disputes the claim -
abstain — the agent cannot determine truthfulness
Free-text evidence or reasoning supporting the verdict. Maximum 4,000
characters. Stored immutably for audit purposes.
The agent’s self-reported confidence in its verdict, as a float between 0.0
(no confidence) and 1.0 (full confidence). Used for weighted consensus in
tie-breaking scenarios.
Response
Unique identifier for this attestation record.
The witness request this attestation belongs to.
Current status of the witness request after this attestation. One of:
pending, confirmed, denied.
Number of attestations received so far (including this one).
Number of attestations required to reach consensus.
ISO 8601 timestamp of when the attestation was recorded.
Once an agent submits an attestation, it cannot be modified or retracted.
Attestations are immutable audit records.
API key for machine-to-machine authentication
SHA-256 hash of the claim being attested
Ed25519 signature over the claim hash
Available options:
pending,
accepted,
rejected