Getting Started

Node Management

Models

Tasks & Inference

Streaming

Developer Documentation

This documentation covers the REST APIs and WebSocket protocols exposed by the csasq NODES edge worker runtime. All endpoints are strictly scoped under /api/v1.

Authentication

Because these nodes run on publicly addressable IPv4/IPv6 space without a AI Platform overlay, application-level security is critical. Every request MUST be authenticated using a statically provisioned Bearer token.

Authorization: Bearer <STATIC_NODE_TOKEN>
Tokens are generated during the automated node provisioning phase (Ansible) and cannot be rotated via the API. If a token is compromised, the node must be rebuilt.

Standard Error Responses

The API adheres to standard HTTP status codes. All error responses return a uniform JSON structure.

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid or missing Bearer token.",
    "request_id": "req_88ab29f1"
  }
}
Status CodeDescription
401 UnauthorizedMissing or invalid token.
403 ForbiddenValid token, but lacks scope (e.g., trying to unload a locked model).
422 Unprocessable EntityValidation error in JSON payload.
429 Too Many RequestsExceeded rate limits (Max 50 HTTP req/sec).
503 Service UnavailableNode is currently restarting its ONNX runtime.