Zeq911

Emergency dispatch optimization. Zeqond-stamped incident logging, nearest-resource allocation using R(t)-weighted distance metrics, priority queuing by severity.

Endpoint	POST /api/emergency/911
Auth	api-key
Rate limit	60/min
Category	emergency

Parameters

Name	Type	Required	Description
location	object	Yes	{ lat, lng } incident location.
incidentType	string	Yes	'medical', 'fire', 'police', 'hazmat', 'multi-agency'.
severity	number	Yes	Severity 1-5 (5 = life-threatening).
callerInfo	object	No	{ phone, name, callback }

Returns

{ incidentId, dispatchedUnits, eta_min, priority, zeqond, auditTrail }

Example

curl -sS -X POST \
  -H "Authorization: Bearer zsm_..." \
  -H "Content-Type: application/json" \
  -d '{
  "location": {},
  "incidentType": "<incidentType>",
  "severity": 0,
  "callerInfo": {}
}' \
  "https://zeqsdk.com/api/emergency/911"

This protocol is a named building block — one of the operations you compose inside a state contract. Call it directly with the request above, or invoke it from a contract that fires on your machine's clock. Browse the whole library at GET /api/protocols; fetch this one at GET /api/protocols/zeq-911.