Developers
The platform is an API your engineers can build against.
Everything Versidon does inside a workspace — submitting work, retrieving a result with its evidence attached, connecting a document source, reaching an internal tool — is available programmatically, inside your own tenant, under the same entitlements and the same audit log.
API CREDENTIALS, REFERENCE DOCUMENTATION AND A SANDBOX WORKSPACE ARE PROVIDED DURING ONBOARDING
Surfaces
Work API
Submit a piece of work — a credit memo, a covenant test, a research brief, a case narrative — against a workspace, and retrieve the result when it completes. Every claim in the result carries the citations it was built from.
Knowledge API
Register document sources and push documents in. Entitlements are carried with the document and enforced at query time, so a source connected through the API answers exactly as it does in the system it came from — no broader.
MCP support
Expose your internal tools to the agent over the Model Context Protocol. Each tool is registered with its own least-privilege identity, an allowlist of callers and an entry in the audit log for every invocation.
Webhooks
Subscribe to workspace and audit events — work accepted, draft written, review requested, content accepted by a person, entitlement decision recorded — and drive your own queues and case systems from them.
Identity and provisioning
Single sign-on over OIDC, and user and group provisioning over SCIM. Roles, segregation of duties and entitlement holders come from your directory rather than being re-declared in a second place.
Telemetry
Traces, metrics and logs export over OpenTelemetry to the collector you already run. Agent runs, retrievals and tool calls appear as spans, so latency and failure show up in your own dashboards.
Your tenant
The platform deploys into your own tenant, in the region you nominate. Documents and derived indexes stay inside that boundary and are never used to train a shared model.
Versioned and evaluated
Agents, prompts and policy sets are versioned artefacts. A version is blocked from publish when its evaluation suite falls below threshold, and rolls back in one step — through the API as well as the console.
Illustrative
Submit a piece of work. Get back a result you can defend.
The exchange below is illustrative — it shows the shape of a request and of the result it returns, not a live endpoint. Your tenant’s host, tokens and the full field reference are issued at onboarding.
REQUEST
POST /v1/work
Host: $VERSIDON_API_HOST # your tenant's host, issued at onboarding
Authorization: Bearer $VERSIDON_API_TOKEN
Content-Type: application/json
{
"workspace": "credit",
"task": "covenant_test",
"subject": { "obligor_id": "OBL-4471", "period": "2025-Q2" },
"sources": ["facility_agreement", "compliance_certificate"]
}RESULT
{
"id": "wrk_01J9...",
"status": "completed",
"attribution": "agent", // marked, and reversible until a person accepts it
"findings": [
{
"covenant": "Net leverage",
"threshold": "<= 3.50x",
"observed": "3.71x",
"result": "breach",
"citations": [
{
"source": "compliance_certificate",
"document_id": "doc_8812",
"page": 2,
"quote": "Consolidated Net Leverage Ratio: 3.71x",
"uri": "versidon://credit/doc_8812#p2"
},
{
"source": "facility_agreement",
"document_id": "doc_4103",
"page": 47,
"quote": "shall not exceed 3.50:1.00 as at any Quarter Date",
"uri": "versidon://credit/doc_4103#p47"
}
]
}
],
"requires_acceptance_by": "entitlement:credit.covenant_review"
}Rules the API keeps
- A result without citations is an error, not a result
- Every finding returned by the Work API carries the passages it was built from. If the agent cannot ground a claim, the field comes back unresolved with the reason — it is never filled in from the model's own recollection.
- Agent-written content is marked in the payload
- Results are attributed to the agent and stay reversible until a person accepts them. Acceptance is its own API call, made by the holder of the named entitlement, and it lands in the audit log with actor and timestamp.
- The API cannot outrank an entitlement
- A token is scoped to a workspace and inherits the entitlements of the identity behind it. Irreversible steps — releasing a payment, filing a report, approving a facility — return a prepared pack and stop; they are never completed by an API call.
Getting access
Access is provisioned with your tenant, not from a signup page.
Because the API answers with your own documents under your own entitlements, credentials are issued against a tenant rather than handed out publicly. Reference documentation, the event catalogue for webhooks, the MCP registration guide and a sandbox workspace are provided during onboarding. Ask for technical access and an engineer will take your integration questions directly.