OpenAPI 3.1 · OMNIA 0.11
Anything can plug in.
Physical sensors, applications, files, scientific instruments, provider APIs, and future adapters share one measurement contract. OMNIA keeps raw observation, calibration, uncertainty, inference, consent, and lineage visibly separate.
1. Register source
Declare ownership, rights, reliability, geography, and permissions.
2. Register device
Describe hardware, transport, quantities, clock, channels, firmware, and calibration references.
3. Send observations
Post one or many typed observations with UCUM units and an idempotency key.
4. Operate connectors
Schedule feeds, retain cursor checkpoints, prevent overlap, retry failures, and inspect permanent run receipts.
Universal observation example
POST /v1/ingest/observations
Idempotency-Key: sensor-reading-0001
{
"sourceId": "my-lab",
"deviceId": "accelerometer-01",
"modality": "sensor",
"observations": [{
"quantityKind": "acceleration",
"value": [0.01, -0.03, 9.80],
"unit": "m/s2",
"evidenceClass": "observed_physical"
}]
}
Download the complete OpenAPI JSON · Read integration capabilities · Inspect connector health · Open the living OMNIA map · Open NOUS Intelligence
Claim IntelligenceTrace the statement. Inspect the sources. Follow the outcome.
See what connects.
One continuous path from a public statement to reusable knowledge.
Give your data a track record.
Track a claim to see real sources and outcomes connected here. No example findings are mixed into your data.
Owner-reviewed outcomes · Connections show recorded lineage, not causation. Motion is decorative; it does not represent measured EFVT or live transfers.