ZeqFleet — Device Fleet Management

Device sync, SCADA, metering, fault detection.

• Protocol ID — zeq-iot-fleet
• Category — IoT
• Endpoint — GET /api/iot/fleet/status
• Auth — api-key
• Rate limit — 30/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Fleet-wide IoT device management. Monitor health, sync status, and firmware across thousands of devices — all coordinated on the Zeqond grid.

Signature

Request

GET /api/iot/fleet/status

Param	Type	Required	Default	Description
fleetId	string		—	Fleet group identifier.

Response

{ devices, online, synced, avgDriftMs, alertCount, lastSyncZeqond }

Runnable example

curl -sS \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  "https://api.zeq.dev/api/iot/fleet/status"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/iot/fleet/status in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqFleet — Device Fleet Management alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqFleet — Device Fleet Management as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.