Developer docs: API, MCP and connectors

What you can build

Push data

Send readings from scripts, gateways, PLC bridges and cloud functions with one HTTPS call to the ingest API.

Quickstart in three steps

Everything below is plain HTTPS with JSON. Ids are UUIDs, and a key only ever sees its own account's data.

Create an API key
In the app, open Settings and create a key with the read, write and ingest scopes. The secret starts with iq_live_ and is shown once. Keep it in an environment variable:
shell
```
export INDUQT_API_KEY="iq_live_…"
```

Create a site and a machine

A site is a plant or building; a machine belongs to one site. Note the id each call returns.

POST /v1/sites

curl -X POST "https://api.induqt.ai/v1/sites" \
  -H "Authorization: Bearer $INDUQT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Pleasanton plant",
  "location": "Pleasanton, CA",
  "timezone": "America/Los_Angeles"
}'

POST /v1/machines

curl -X POST "https://api.induqt.ai/v1/machines" \
  -H "Authorization: Bearer $INDUQT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "siteId": "6f1c2c0e-4b1a-4c55-9d0e-1f2a3b4c5d6e",
  "name": "Boiler B-101",
  "family": "boilers",
  "externalId": "B-101",
  "make": "Cleaver-Brooks",
  "model": "CBEX Elite"
}'

Send a reading

Address the machine by its id or by your own externalId. Signal keys are created on first use.

POST /v1/ingest

curl -X POST "https://api.induqt.ai/v1/ingest" \
  -H "Authorization: Bearer $INDUQT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "machine": "B-101",
  "siteId": "6f1c2c0e-4b1a-4c55-9d0e-1f2a3b4c5d6e",
  "ts": "2026-10-27T03:12:09Z",
  "values": {
    "steam_pressure": 112.4,
    "steam_flow": 2.1,
    "flue_o2": 3.2,
    "stack_temp": 410
  }
}'

Then read it back, record a window and ask for an analysis in the full quickstart.