ZeqSLAM

Kinematics, SLAM, manipulation, swarm, PID.

• Protocol ID — zeq-slam
• Category — Robotics
• Endpoint — POST /api/robotics/slam
• Auth — api-key
• Rate limit — 15/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Simultaneous Localization and Mapping on Zeqond frames. LiDAR/camera fusion, loop closure detection, graph-based optimization with R(t)-weighted scan matching.

Signature

Request

POST /api/robotics/slam

Param	Type	Required	Default	Description
sensorData	object	✓	—	LiDAR point cloud and/or camera frames.
odometry	object		—	Wheel/IMU odometry estimates.
mapId	string		—	Existing map to localize against.

Response

{ pose, map, loopClosures, uncertainty, zeqond }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "sensorData": {},
  "odometry": {},
  "mapId": "<value>"
}' \
  "https://api.zeq.dev/api/robotics/slam"

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/robotics/slam in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqSLAM alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqSLAM 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.