Documentation

Push agents into the Vidimus inventory from your own configuration database or governance tool. The endpoint accepts up to 500 agents per call and answers 202 with the identifier of the sync run it started.

POST /api/v1/registry/agents
Authorization: Bearer <organisation key>
Content-Type: application/json

{
  "agents": [
    {
      "external_id": "cmdb-4821",
      "name": "Claims triage assistant",
      "description": "Routes motor claims under 25 000 EUR.",
      "endpoint_url": "https://agents.example.com/claims",
      "protocols": ["http"],
      "owner": "claims-ops@example.com",
      "region": "europe-west1"
    }
  ]
}

The key is issued from Settings, shown once, and stored only as a hash. Agents arrive as drafts: nothing a person has already accepted is overwritten, and a change coming from your side opens a review item instead of silently editing the declaration.

The machine-readable description of the request and every response lives at /api/v1/openapi as an OpenAPI 3.1 document.

Every pack carries the hash of its own content. Anyone holding a pack can ask the platform whether that hash is the one on record, which is what makes the pack checkable after it has left your estate.

GET /api/evidence-pack/<reviewId>/verify

{
  "content_sha256": "…",
  "signature_ed25519": "…",
  "signing_key_id": "vidimus-pack-…",
  "verified": true
}

The public half of the signing key is published at /.well-known/vidimus-signing-keys.json, so a third party can check the signature without asking us for anything.

The pack is a PDF with a fixed section order, so a reader who has seen one can find their way around any other. Sections one to nine: executive summary, agent profile, risk breakdown, regulatory coverage, test results, control checklist, the reviewer decision, the audit trail, and an appendix naming the corpus, pattern bank and judge model versions the run used.

Two properties matter to an auditor. Each pack is immutable and numbered, so re-issuing produces a new version rather than editing the old one. And every obligation carries the verbatim regulation text it came from, so a disagreement is about the law rather than about what we summarised.

The classification record is a separate immutable document covering the legal classification, the operator role, the Article 5 screening, Article 50 transparency and the Article 6(3) derogation, with the hash of its own content printed on page one.

Vidimus reaches your agent over the interface it already exposes: plain HTTP request and response, server-sent event streams, the Model Context Protocol, or an agent-to-agent endpoint with its published card. Credentials are held in an EU key store and never written to logs or into a pack.

Tool calls are observed on the wire, so an agent that claims to escalate and does not is caught by the transcript rather than by its own description of itself.