DEVELOPERS · API

REST API.
Evidence in every response.

Versioned REST endpoints for application integration. Every response carries machine-readable evidence, provenance, authority scope, and record state.

← Developers MCP Surface

AUTHENTICATION

Bearer token. Project scoped. Environment isolated.

Every Veritan API request authenticates with a project credential. Development and production environments are strictly isolated. Credentials are scoped to explicit capability sets and are rotatable and revocable from the Console.

EXAMPLE — NOT A PRODUCTION ENDPOINTHTTP

Authorization: Bearer vrtn_live_••••••••••••

# Development credentials use:
Authorization: Bearer vrtn_dev_••••••••••••

REQUEST MODEL

Structured request. Evidence-bearing response.

Every Veritan API request specifies the record, the capability scope, and the evidence fields required. The response includes the structured result plus machine-readable evidence so downstream systems can verify, not just consume.

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": "<record-id>",
    "state": "active",
    "version": 3
  },
  "evidence": {
    "provenance": {
      "origin": "...",
      "chain": [...],
      "verified": true
    },
    "authority": {
      "issuer": "...",
      "scope": ["verify", "read"],
      "valid_until": "..."
    },
    "state": "active"
  },
  "verified_at": "2026-08-18T00:00:00Z",
  "request_id": "<request-id>"
}

API SURFACE

Capabilities available via the API.

The Veritan API exposes the core platform capabilities through a consistent versioned surface. Actual endpoint paths, request schemas, and response fields are documented in the developer reference once available.

RECORDS

Create, read, update, and verify records. Every response includes the current state and evidence chain.

EVIDENCE

Request evidence for a record: provenance chain, authority scope, state transitions, and verification timestamps.

PROVENANCE

Inspect the complete unbroken provenance chain for any record. Traceable to origin.

AUTHORITY

Verify the authority scope of a given credential or operator action against a record.

CREDENTIALS

Manage project credentials: list, create, scope, rotate, and revoke. Never returns credential values in responses.

USAGE

Per-project request counts, evidence lookups, and audit log entries for billing and compliance review.

ENVIRONMENTS

Development and production are strictly separated.

Development credentials are clearly prefixed and never valid against production data. Production credentials are scoped explicitly and must be rotated through the Console. Mixing environments is prevented at the platform layer.

DEVELOPMENT

`vrtn_dev_••••••••••••`

Safe integration environment. Data is isolated. No production evidence.

PRODUCTION

`vrtn_live_••••••••••••`

Live platform access. Full evidence, provenance, and authority. Scoped and audited.

AUDIT

`vrtn_audit_••••••••••••`

Read-only evidence inspection. Evidence and provenance are readable; no record mutations.

ERROR MODEL

Structured errors. Machine-readable codes.

Veritan API errors return structured JSON with machine-readable codes, the affected scope, and resolution guidance. Error categories are stable across API versions.

EXAMPLE ERROR RESPONSEJSON

→ 403 Forbidden
{
  "error": {
    "code": "authority.insufficient_scope",
    "message": "Credential scope does not permit this operation.",
    "scope_required": "verify",
    "scope_held": ["read"],
    "request_id": "<request-id>"
  }
}

Explore the MCP surface.

MCP ↗Events

REST API.Evidence in every response.