LiveVidimus Sensor
Every measurement, as the sensor sent it.
Loggers, meters and weighbridges send their measurements through the API. Vidimus records each measurement separately and anchors it automatically, within five minutes.
€15 per sensor or logger per month · the first one free · unlimited measurements
What it does.
You create each measurement source once in the app, with a unit, a range and its own key. After that, the device or your measurement platform sends its measurements to the API. Each measurement gets a fingerprint and is anchored within five minutes. In a dispute, you show the series of that device.
- measurement source
- cold store 3 · logger KC-03
- measurement
- 2.4 °C
- range
- −30 to 40 °C
- time
- 4 September 2026 · 14:05:00 (UTC+2)
- signed
- key of the measurement source
- outcome
- unchanged · timestamp + Bitcoin anchor
Four steps, the same for every measurement.
- 01
Fingerprint
sha-256 · per measurementEach measurement gets its own fingerprint, over source, time, value and unit. A corrected value gives a different fingerprint.
- 02
Signature
ed25519 · key of the measurement source, kept by VidimusEach measurement source has its own key and records only for itself. The key can be revoked at any time.
- 03
Timestamp
rfc 3161 · per five-minute groupAn external timestamping service signs the group the measurement is in, every five minutes. The time does not come from you and not from us. Then the qualified timestamp from GLOBALTRUST (eIDAS) follows, per group, for customer organisations, usually within six hours.
- 04
Anchor
ledger (hash chain) → opentimestamps → bitcoinThe root of the group goes into our ledger, where each entry hashes the previous one, and via OpenTimestamps into Bitcoin. Any change or deletion shows up for anyone who checks, even if we were to try it ourselves.
Every step can be recomputed, even without Vidimus. All seven steps, from identity to deletion
Specifications and price.
- transport
- HTTPS · REST API · key in the x-api-key header
- endpoints
- POST /measurements · POST /measurements/batch
- format
- JSON · fixed schema: source, time, one number, unit
- range
- a unit and a range per measurement source; anything outside is rejected
- rate
- at most one measurement every ten seconds per device, in ascending time order
- after being offline
- send them together later via batch, measurements up to 24 hours old
- anchored
- anchored within five minutes
- testing
- test key that records nothing; response with "proef": true
- retention
- ten years per logbook by default, adjustable
- price
- €15 per device per month with at least one measurement · the first one free
What it often comes down to.
Examples, not limits: Vidimus is one product for every type of record.
What you want to know.
What is a measurement, and what is not?
A measurement is one number, such as a temperature, weight or position, from a sensor or logger that you created with a unit and a range. You pay per device, not per measurement. Everything a system or phone sends with its own content is a record.
What if the device is offline for a while?
Later, send the measurements that the device or your platform stored in the meantime together through /measurements/batch, in ascending time order and no older than 24 hours. The time in the measurement is what the device reported; the timestamp of the group shows when the measurement was anchored.
Do I have to replace my measurement platform?
No. Your loggers and your platform stay. The platform or the device also sends each measurement to Vidimus. You first test the integration with a test key that records nothing; then the administrator creates the live key.
Start with one device: the first sensor or logger is free.
No payment details needed. A director identifies your company once with the Belgian eID; then you create a measurement source and test the integration with a test key.