Build toward
verifiable AI systems.
The Veritan developer surface defines how applications, AI agents, and external systems are intended to access machine-readable evidence, provenance, authority, and state.
Four access channels. One evidence model.
Choose the right interface for your integration context. Every channel delivers evidence-bearing responses against the same platform model.
Three machine interfaces. One evidence model.
The public developer experience presents the intended integration contracts for traditional applications, AI-agent workflows, and external systems. Production availability is stated only where separately evidenced.
REST interface
The API contract is designed around authenticated, scoped requests and machine-readable evidence responses for application integration.
Agent interface
The MCP contract is designed for tool discovery, scoped authorization, and structured evidence-bearing responses that AI agents can inspect directly.
Event interface
The Events interface is designed for state-change notification, replay-aware integration, and auditable external-system synchronization.
From scoped credential to evidence-bearing response.
The example below illustrates the intended shape of a Veritan integration. It is not a claim that this endpoint or credential format is currently production-operational.
POST /v1/records/verify
Authorization: Bearer vrtn_example_••••••••••••
Content-Type: application/json
{
"record_id": "<record-id>",
"evidence_scope": ["provenance", "authority", "state"]
}
→ 200 OK
{
"record": { "id": "...", "state": "active" },
"evidence": { "provenance": {...}, "authority": {...} },
"verified_at": "<timestamp>"
}What the platform is designed to make consistent.
Across API, MCP, and Events, Veritan's target contract is consistent evidence, authority, provenance, state, and audit semantics. The public site documents that architecture without overstating production availability.