Developers · pilots

API overview for institutional pilots

AskVerum™ API access is enterprise/pilot gated — not a self-serve retail tier. This page documents the public contract shape so security and platform teams can plan embedding. Contact info@ask-verum.com for credentials and DPA.

Auth

Browser users: Google OAuth via Supabase. Programmatic pilots: Bearer auth on API routes. Full SAML/OIDC SSO is on demandfor contracted enterprise — today's shipped path includes org membership plus an optional SSO lifecycle webhook, not a complete IdP login UI.

Core routes (overview)

POST /api/v1/query

Start an investigation (auth required). Body includes question text and optional attachments per product policy.

GET /api/v1/results/{queryId}

Fetch investigation status and structured result payload for the authenticated owner/org member.

POST /api/v1/export/pdf

Server-side PDF export of an investigation the caller can access.

POST /api/v1/enterprise/sso/lifecycle

Enterprise SSO lifecycle webhook (shared secret) — provision/deactivate users. Not full SAML/OIDC.

Provenance expectations

Each investigation carries algorithm version metadata (e.g. VTS-2.4, VBE-2.0). Exports can include claim-ledger annex and method notes. Treat outputs as decision-support: Trust Score is a governance composite, not factual certification.

Detailed OpenAPI and sandbox keys ship under NDA for active pilots. Security questionnaires: Trust Center.