POST /api/community-operators/:id/promote
this), and an explicit { confirm: true } is mandatory: a machine may PROPOSE and the vote may APPROVE, but a person must take this deliberate step. The actual operator-registry.json merge remains a maintainer commit (sou
| Method | POST |
| Path | /api/community-operators/:id/promote |
| Auth | user |
| Group | Compute · Community Operators |
Request
curl -X POST https://zeqsdk.com/api/community-operators/CONTRACT_ID/promote \
-H "Authorization: Bearer $ZEQ_KEY" \
-H "Content-Type: application/json" \
-d '{ }' # request body — see description
Needs a machine key — mint one free:
curl -X POST https://zeqsdk.com/api/demo-key/mint, then spin up your machine.
Generated from the node's own route registry (GET /api/endpoints) — this path is live.