Skip to main content

Developer preview / fictional API

Evidence that connects.

A proposed technical direction for engineering partners, asset platforms and recurring inspection programmes.Prototype 0.1. No production API.

01 / Data model

A finding without context is just a file.

The proposed model connects the structure, asset, inspection route, position, media, equipment state and engineering review. This would allow evidence to be compared across projects and inspection cycles.

GET /v1/assets/{asset_id}/evidence 200
{
  "asset": "bridge-07/main-cable-a",
  "run": "inspection-2026-014",
  "position_m": 183.42,
  "capture": {
    "type": "visual_still",
    "media_id": "ev_02847",
    "device_state": "verified"
  },
  "observation": {
    "class": "surface_anomaly",
    "review": "engineer_required"
  }
}

02 / Event stream

Live events, kept distinct.

  1. 01

    Position event

    Route, direction, speed and changes between segments.

  2. 02

    System event

    Connection, power, sensor state and technical warnings.

  3. 03

    Evidence event

    Capture, annotation, review status and export reference.

03 / Integration

Designed for partners, not lock-in.

The proposed direction includes project-specific exports, immutable media references and interfaces to asset management, GIS and reporting systems. Production formats and contracts have not been defined.

  • REST
    Draft
  • Webhooks
    Draft
  • Media export
    Prototype
  • SDK
    Future
Explore the platform