ZeqBandwidth — Pulse-Modulated Allocation

Zeqond-grid transport, mesh, routing, DNS.

• Protocol ID — zeq-bandwidth
• Category — Network
• Endpoint — POST /api/network/bandwidth/allocate
• Auth — api-key
• Rate limit — 60/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Bandwidth allocation modulated by HulyaPulse. High-priority traffic gets the peak of the R(t) cycle; background traffic uses the troughs. Fair by physics.

Signature

Request

POST /api/network/bandwidth/allocate

Param	Type	Required	Default	Description
streamId	string	✓	—	Data stream identifier.
priority	number	✓	—	Priority level (1–10). Higher = allocated at R(t) peaks.
requestedBps	number	✓	—	Requested bandwidth (bytes/sec).

Response

{ allocatedBps, phaseSlot, R_t_at_slot, utilizationPct }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "streamId": "<value>",
  "priority": 0,
  "requestedBps": 0
}' \
  "https://api.zeq.dev/api/network/bandwidth/allocate"

Integrate

1. Mesh health probe — tick against this endpoint each Zeqond and alarm on missing edges.
2. Routing seed — inject the returned topology into a BGP/QUIC shim for pulse-aware routing.
3. DNS drift — detect stale propagation by comparing pulse-stamps across resolvers.

Seeds

• Near — wrap /api/network/bandwidth/allocate in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqBandwidth — Pulse-Modulated Allocation alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqBandwidth — Pulse-Modulated Allocation 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.