Developers · Integrations

Connect your data.

YAS ingests live machine data from telematics platforms, OEM feeds, and edge SDKs — normalized into the ODD Engine before scoring. Certified connectors are expanding; sandbox access is available for pilots.

Connector catalogue

Bring data in your way.

Whether your fleet runs on a major telematics platform or a bespoke robotics stack, there is a path in.

  • Geotab

    Telematics

    Pilot
  • Samsara

    Telematics

    Pilot
  • Motive

    Telematics

    Roadmap
  • YAS SDK

    Edge capture

    Live
  • Robotics OEM feed

    Custom

    Pilot
  • SFTP batch

    Custom

    Live

Integration paths

Three ways to connect.

Certified connectors

Pre-built connectors for major telematics platforms. Map your account, and trips flow into scoring automatically.

  • GPS, CAN, and driver-behaviour streams
  • Account-level mapping
  • Managed schema upgrades

Events API & SDK

For operators who emit their own telemetry. Capture at the edge with the SDK, read scores over the API.

  • Edge capture on iOS / Android
  • Read scored trips over REST
  • Best for AV and robotics operators

Custom & batch

Non-standard schemas? Send normalized batches over SFTP, or co-engineer a custom feed with our team.

  • SFTP batch ingestion
  • Co-engineered schema mapping
  • Robotics OEM feeds

How onboarding works

From feed to scored fleet.

  1. 01

    Map the source

    We map your platform account, device feed, or schema to the ODD Engine inputs.

  2. 02

    Normalize

    Trips are cleaned, map-matched, and ODD-tagged so scoring sees consistent inputs.

  3. 03

    Score

    Each trip rolls into one explainable AURA score, ready to read over the API.

  4. 04

    Certify

    Validated connectors join the catalogue; your fleet runs in production.

Don't see your platform?

Tell us your telematics provider, OEM, or schema. We'll scope a connector or custom feed — and reply within 48 hours.