Developer APIs
One governed data contract for the whole estate.
PrecisionDCOS exposes read, streaming, command, export and webhook APIs over a common data contract. Every value carries identity, time, quality, authority and evidence — so what you build on it stays trustworthy.
The common data contract
Every value published by the platform is self-describing and governed — not a bare number on a topic.
Identity, time, quality, authority, evidence
A value is never delivered alone. It arrives with where it came from, when it was true, how much it can be trusted, whether it can be acted on, and the evidence trail behind it. This contract is what lets operations and AI act on the data without re-deriving trust every time.
API families
Five governed surfaces, all sharing the same identity, tenancy and evidence model.
- Read APIs
- Query current and historical values, assets, dependencies, incidents and evidence with tenant-scoped access.
- Streaming
- Subscribe to governed real-time updates and events over durable streams with backpressure and replay.
- Command APIs
- Request bounded, fenced actions through engineered command paths — never a bypass of protective controls.
- Export & publication
- Publish governed datasets to lakes, warehouses and AI pipelines with lineage and quality preserved.
- Webhooks
- Receive signed callbacks on incidents, state changes and closure with linked evidence references.
Data quality is a first-class field
Every value carries an explicit quality state so consumers never act on data they cannot trust.
Value is trusted and within expected behavior.
Value is questionable; confidence is reduced.
Value is invalid and must not drive action.
Value has not updated within its expected interval.
Point is intentionally removed from active monitoring.
Value is injected for test and clearly flagged as non-live.
Example value payload
A single point read, showing the full governed contract.
{
"point": "site-04.chw.loop-a.supply-temp",
"value": 7.2,
"unit": "degC",
"timestamp": "2026-08-07T14:22:05.118Z",
"quality": "GOOD",
"identity": {
"site": "site-04",
"domain": "mechanical",
"asset": "chiller-plant-a"
},
"authority": {
"controlClass": "S4",
"commandable": false
},
"evidence": {
"source": "nx-node-2",
"collector": "bacnet-collector-11",
"trace": "ev_9f2c81a4"
}
}Access & governance
APIs are governed the same way the platform is — scoped identity, explicit authority and full auditability.
- Tenant-scoped identity and least-privilege access tokens
- Command APIs are fenced, bounded and never bypass protection
- Every request and action is audited with linked evidence
- Residency-aware: data stays where policy requires
Build on governed data
Request API documentation and a sandbox scoped to a reference environment.