Skip to main content
DEVELOPERS

Build on
Veritan.

Integrate machine-readable evidence, provenance, and authority into applications and AI systems via API, MCP, and event streams.

GETTING STARTED

From credential to first response.

Every Veritan integration begins with an authenticated credential, a scoped project, and a first request that returns evidence-bearing structured data.

EXAMPLE — NOT A PRODUCTION ENDPOINTHTTP
POST /v1/records/verify
Authorization: Bearer vrtn_live_••••••••••••
Content-Type: application/json

{
  "record_id": "<record-id>",
  "evidence_scope": ["provenance", "authority", "state"]
}

→ 200 OK
{
  "record": { "id": "...", "state": "active" },
  "evidence": { "provenance": {...}, "authority": {...} },
  "verified_at": "2026-08-18T00:00:00Z"
}
CAPABILITIES

What every integration can access.

The Veritan platform exposes a consistent capability layer across all integration surfaces. The same evidence, authority, provenance, and state are accessible via API, MCP, and Events.

AUTHENTICATION
Bearer token authentication with project-scoped credentials. Separate development and production environments.
EVIDENCE RESPONSES
Every API response includes machine-readable evidence: provenance chain, authority scope, record state, and verification timestamp.
VERSIONING
Stable versioned API surfaces with changelog. Breaking changes are announced with a migration path.
RATE & USAGE
Per-project usage tracking with configurable limits. Audit log for every interaction.
ERRORS
Structured error responses with machine-readable codes, scope context, and resolution guidance.
SECURITY
All traffic over TLS. Credentials are scoped, rotatable, and revocable. No plaintext secrets.
CHOOSE YOUR SURFACE

API, MCP, or Events.