Node key lifecycle v5

Rotate and revoke node telemetry credentials without redeploying the platform.

Use per-node API keys for agent heartbeat, GPU metrics, power metrics, and incident-triggering telemetry. The secret is only shown once; the database stores a SHA-256 hash.

Create

Create node key

POST to /api/node-keys/create with organizationId and nodeId.

{
  "organizationId": "demo-org",
  "nodeId": "sg-sin-colo-01",
  "name": "Production node agent"
}
Rotate

Rotate node key

POST to /api/node-keys/rotate. Optionally pass oldKeyId to revoke the old key in the same operation.

{
  "organizationId": "demo-org",
  "nodeId": "sg-sin-colo-01",
  "oldKeyId": "<old-key-id>"
}
Revoke

Revoke key

POST to /api/node-keys/revoke. Revoked keys are rejected by telemetry ingestion immediately.

{
  "organizationId": "demo-org",
  "keyId": "<key-id>"
}
Current node context

Use these IDs for local testing.

NodeNode IDStatusOrg ID
Singapore Colo Node 01sg-sin-colo-01onlinedemo-org
Dar Tower Node 01tz-dar-tower-01onlinedemo-org
Frankfurt Sovereign Nodede-fra-enterprise-01onlinedemo-org
Dubai Enterprise Campus Nodeae-dxb-campus-01degradeddemo-org
Ashburn Edge Nodeus-ash-edge-01offlinedemo-org