ZeqSMS

SMS, VoIP, email, mesh, satellite.

• Protocol ID — zeq-sms
• Category — Communications
• Endpoint — POST /api/comms/sms
• Auth — api-key
• Rate limit — 30/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

HulyaPulse-synced SMS delivery. Encodes payload with R(t) modulation for tamper-evident timestamps. Supports international E.164 routing, delivery receipts, and Zeqond-stamped audit logs.

Signature

Request

POST /api/comms/sms

Param	Type	Required	Default	Description
to	string	✓	—	Destination phone number (E.164 format).
body	string	✓	—	Message body (max 1600 chars, auto-segments).
zeqondStamp	boolean		true	Embed Zeqond timestamp in metadata.

Response

{ messageId, status, zeqond, phase, deliveryEstimate, segments }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "to": "<value>",
  "body": "<value>",
  "zeqondStamp": true
}' \
  "https://api.zeq.dev/api/comms/sms"

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