Skip to content
Control Plane API
Skip navigation
View as Markdown

Control Plane API

One Cypher verb over one HTTP endpoint mints addresses, sets resolver rules, reads logs and cuts access.

Published

In this chapter

Control Plane API Documentation

Everything you change about an agent goes through one Cypher procedure, whisper.agents, posted to one endpoint. The same endpoint answers graph reads, so one key and one URL cover both provisioning and investigation.

bash
curl -s https://graph.whisper.online/api/query \
  -H 'X-API-Key: whisper_live_...' \
  -H 'content-type: application/json' \
  --data-binary @- <<'JSON'
{"query": "CALL whisper.agents({op: 'list', args: {kind: 'agents'}})"}
JSON

The request envelope has the wire format: how to build the map literal by hand, and the columns every answer arrives in. Keys and scopes covers where a key comes from and which authority each call needs. The operations chapter carries one page per operation, each with its arguments and its return columns. When a call comes back with ok: false, error codes says what the code means and whether the call is worth sending again.

Two sides of the plane need no key at all. Keyless endpoints is the verification, registry and log surface, which anyone can call to check an identity you minted without holding an account here. Discovery files lists the machine-readable manifests an agent reads to find the rest on its own.