Get demo access

Platform · APIs and the fabric

One API for every vehicle you may reach.

A single API connects internal tools, engineers, fleet software and AI agents to the platform. Access rights dictate what each user or service can see. We call this setup the c.technology fabric, linking vehicles, partners and software under precise permissions.

01The API

The same record the screens use.

The screens and the API read the same vehicle record, with the same permissions. Build on it, and you build on the real thing.

What it does

Read, write, follow.

REST Live

Vehicles, status, trips, error codes, maintenance, documents, partners and permissions, to read and to write. Push your own data in the same way. Versioned, with a full OpenAPI reference. Documentation ↗

Live stream Live

A WebSocket stream of status, actions and notifications as the vehicle reports them. Everything stays in sync, re-scoped the moment a permission changes. Described in AsyncAPI. Stream reference ↗

History Enterprise

Any fields of any vehicle you may see: as CSV over REST, a month per request, or the whole database as a dump. For your data warehouse, your engineers, or a model you train.

Webhooks Coming

We call your endpoint when something happens on a vehicle, instead of you asking.

Who may call it

Always with someone's permissions.

API keys Live

Scoped to an organisation or to one vehicle. A manufacturer manages them in the OEM Suite's developer section, and a dealer can work over the API just the same, for the vehicles it was granted.

Apps, signed in over OAuth Coming

An application authenticates over OAuth and then acts on behalf of a user, with exactly that user's permissions: the same REST API, the live stream and webhooks.

Single sign-on Enterprise

Your staff sign in with your own identity provider, over OAuth or SAML. One fabric login per person, across every manufacturer that grants access. Access and permissions →

For AI

A toolbox for agents.

AI toolbox Coming

An MCP connector that hands the platform to AI agents directly, with the permissions of whoever runs them. Today, the query API already answers fleet questions. AI and agents →

Build on it

Your integration is one prompt away.

Give an AI assistant the API and a key, and describe what you need. A sync with your ERP, your shop's till, or a shipyard's lift: one of our customers launches boats this way.

ComingApps that sign in over OAuth and act for each user, and running such small programs in our cloud, so you host nothing.

An example · a shipyard, one afternoon

Shipyard, to an AI assistant

Here is the API and our key. When an owner books a launch, put the boat on the next morning's lift plan.

The assistant

Done. Bookings arrive over the live stream and the lift plan updates itself. Only the boats the yard may see.

APIThe same API, no integration project

02The c.technology fabric

More vehicle reach under your rules.

One vehicle has many parties around it: you, its owner, the dealer, the workshop, a fleet, an insurer, the apps they all use. The fabric connects each of them to the vehicle, and only to what they were given.

  • You, the manufacturerYour vehicles, your rules, in your OEM Suite. You decide who else connects.Sets the rules
  • Dealers and workshopsOne fabric login for every brand they sell, each brand's vehicles as that brand allows.Granted by you
  • Fleets and rentalsOne API and one key for every vehicle granted to them, whoever built it.Granted by you or the owner

One vehicle

Its record, its history

  1. Permission
  2. Capability
  3. Entitlement

Checked on every call, for every party

  • The ownerAll their vehicles in one app, whatever the brand. Their own vehicle's data, by right.Theirs, by law
  • Services the owner choosesAn insurer, a charging service, an app they like: access the owner gives, and takes back.The owner's choice
  • Your own apps and agentsBuilt on the same API, by your team or anyone you allow, with the same rules.Your key

Nothing connects that you did not allow.

Data leaves only along a grant you or the owner made, and only the fields and the part of the past that grant covers. Revoke it and it ends at once. No manufacturer ever sees another's vehicles. Access and permissions →

The Data Act asks for it anyway.

Since 12 September 2025, owners may access their vehicle's data and share it with services they choose. The fabric is that mechanism, built in: per vehicle, revocable, with the compensation between businesses you set. Compliance stays with you. The EU Data Act →

And everyone can build on it.

Multi-brand dealers manage every brand through a single login, mixed fleets use one key, and apps and AI agents run on the same API. The ecosystem around your vehicles grows without you building any of it. One login for dealers →

03Data access for fleets

Fleets get your data. You set the terms.

Fleets read your vehicles' data today, exactly as far as they were granted. Offering it to fleets you do not work with yet, and charging for it, is where this goes next.

Today

  • A fleet on the platform has nothing to do. Its vehicles are in its Partner Hub, whoever built them. Live
  • A fleet with its own tools connects with its key and reads what it was granted, nothing more. Live

Next

  • Offer parts of your data to fleets you choose, and charge them for it, at your price. There is no billing yet. Coming
  1. 1 PermissionWho may ask: granted by you or by the owner
  2. 2 CapabilityWhat the vehicle can give
  3. 3 EntitlementWhat they have paid for, at the price you set

A fleet that owns its vehicles gets their data free, as the EU Data Act requires. A price is for third parties, and has to stay reasonable. The EU Data Act →

An example · a small fleet, one afternoon

Fleet manager, to an AI assistant

Here is the API and here is my key. Put my twelve scooters into our dispatch sheet, with charge and odometer.

The assistant

Done. Twelve vehicles from two manufacturers, refreshed from the live stream. Only the fields your key may read.

APIThe same API, no integration project

04Modular

Use what you need. Add later.

Every part of the platform stands on its own and works with the rest. Start with the driver app, or with the API alone, and switch on more when you are ready.

Start with one part. Add the rest when you need it.

Your own app or tool goes on the same API our products use, and your dealers open it with the fabric login they already have.

Yours

Your features, apps, dashboards and integrations

  • Your ERP sync
  • A till in your shop
  • A shipyard's lift plan
  • An AI agent

The API

One key · one format · every vehicle you may reach

Switch on what you need

  • OEM Suite
  • Partner Hub
  • Driver app
  • Services and subscriptions
  • Documents
  • Support
  • Firmware distribution
  • Receivers for your devices

05What stays yours

Your data. Your brand.

You keep both, whatever you decide about us later.

Your data

You own your data.

Every record of every vehicle you built is yours. Download it any time, live or as a full export.

You own itEvery vehicle you built, across your whole fleet
The owner has accessTo their own vehicle, while they own it

Owner access is what the EU Data Act asks for. It comes built in. The EU Data Act →

Your brand

Your name on everything.

Your customers see your brand, not ours. Every app, portal and message goes out as you.

  • Your appIn your Apple and Google accounts, under your listing
  • Your newsTo your partners and owners, under your name
  • Your networkYou choose your partners and their access

We never sell your data, and no other manufacturer will ever see your vehicles. Security and operations →

06Questions

Asked by developers.

Is it one API across manufacturers?

Yes. A key belongs to an organisation, and an organisation sees every vehicle it has been granted, whichever manufacturer built it. A multi-brand dealer or a mixed fleet uses one key and one data format for all of them.

Can a fleet get our vehicles' data without us building anything?

Yes, for what you grant. A fleet on the platform already sees its own vehicles, and a fleet with its own tools connects through the API with its key. Offering parts of your data to other fleets, at a price you set, is coming; there is no billing yet.

Do you offer MQTT or webhooks?

Webhooks are coming. MQTT is coming as a way in, next to Kafka. Today, data comes out over REST and a live WebSocket stream.

What does it cost?

API access is part of the platform. Every connected vehicle is billed on one published ladder, whichever way its data is read. Pricing

Build on the demo.

Talk to our engineers →