Let your agent fetch the proof.
“Go to Vidimus and get me the proof for this disputed case.” Vidimus is built to be used by agents too — Claude, ChatGPT or your own automation. Three layers: a readable summary for models (llms.txt), a fully described API (OpenAPI · Swagger) and an MCP server with ready-made tools. Public facts without a key; your own case files with a separate key for your agent, never your organisation's key.
| The user asks | What the agent does | Key |
|---|---|---|
| “Is record reg_… still untouched?” | GET /verify/{id} → all checks, including the qualified timestamp | no |
| “Show me everything about shipment VAC-2026-007.” | GET /passport/{ref} → timeline across all parties (facts only) | no |
| “Check this evidence bundle from a supplier.” | POST /verify-upload (zip) → outcome + checks | no |
| “Get me the proof for the extra-work order for block B.” | GET /registrations?ref=… → /dossier → /bundle | yes |
| “Is this PDF the version we recorded at the time?” | SHA-256 locally → POST /lookup → match + proof | yes |
| “Record this delivery note and have the recipient sign it.” | POST /registrations → POST /registrations/{id}/share (QR/email) | yes |
| “Show the temperature series of logger TL-0917.” | GET /sources/{id}/reeks → every measurement from that measurement source with its fingerprint (a measurement has no share link) | yes |
| “Set up a task for the driver.” | POST /streams/{id}/opdracht → app link, by email or as a QR code | yes |
Hosted, nothing to install. Give your agent one address and its own key, never your organisation's key. You create it in the app, under Connect. On the AI assistant tab, your assistant gets a key that looks up and checks, or a key that records in one logbook and then only sees what it recorded itself. Revoking takes effect immediately, without touching your systems. Without a key, only the public tools work.
{"mcpServers": {"vidimus": {
"type": "http", "url": "https://app.vidimus.be/mcp",
"headers": {"x-api-key": "${VIDIMUS_MCP_KEY}"}}}}
The key always goes in the x-api-key header (or Authorization: Bearer), preferably from an environment variable, never in a URL.
| Program | Does it work? |
|---|---|
| Claude Code, Cursor, VS Code, Codex | Yes, with the key in the header. The app shows the snippet to copy for each program. |
| Claude in the browser, the Claude app, ChatGPT | Not yet: they ask for a sign-in instead of a key. We are working on it. Until then, they only work for public checks. |
Building an integration with your agent. For a system or device (TMS, WMS, sensor), the administrator first creates it under Connect. Your agent then gets a test key (vks_test_…, server name vidimus-test, environment variable VIDIMUS_TEST_KEY): it records nothing, and every response contains "proef": true (“proef” means test). With connection_status, the agent sees what is ready, and it tests with test_measurement or test_registration until the response contains "aanvaard": true (accepted). Then the system's own code sends one message with the test key. Only then does it say “Test passed”, and the administrator creates the live key. That key belongs in the system as VIDIMUS_API_KEY, never in the chat, in code or in an MCP connection.
Note: we have no Vidimus package on PyPI. Anyone who runs pip install vidimus installs someone else's code. Use only the address above.
Tools: verify_registration · passport · list_registrations · list_streams · get_dossier · get_content · register · connection_status · test_measurement · test_registration · create_share · tamper_check · usage · explain.
User: "Get me the proof of Friday's disputed delivery, container MSKU 452 118-0."
Agent: passport("MSKU 452 118-0") → finds the delivery + the terminal's confirmation
get_dossier(reg_…) → the readable case file
verify_registration(reg_…) → "Unchanged: content, signatures and timestamps match."
Every evidence bundle contains a stand-alone check script (verify_bundle.py, Python 3 with the cryptography package) and the timestamp files (RFC 3161), including the qualified timestamp from a qualified trust service provider on the EU trusted list. An agent — or your IT team — can therefore check without a single connection to us:
python3 verify_bundle.py bundel.zip → GELDIG · 7 van 8 nagerekend (printed in Dutch, a technical status: 7 of 8 recomputed; you compare the Bitcoin block online) openssl ts -reply -token_in -in tijdstempel.tsr -text → time + Merkle root from the timestamping service https://eidas.ec.europa.eu/efda/tl-browser/ → the issuer of gekwalificeerd.tsr is listed as qualified on the EU trusted list