API Reference

Delibera exposes four distinct APIs. Each serves a different role in the protocol.

| API | Base URL | Purpose | |---|---|---| | Worker API | http://localhost:3001 (or Phala TEE endpoint) | Task execution on individual workers | | Coordinator API | http://localhost:3000 (or Phala TEE endpoint) | Proposal management, task dispatch, worker discovery | | Protocol API | https://protocol-api-production.up.railway.app | One-click provisioning, registry queries, agent management | | Ensue Memory API | https://api.ensue-network.ai/ | Shared coordination state (JSON-RPC 2.0 over SSE) |

Authentication

• Worker and Coordinator APIs have no authentication in local mode. In production, they run inside Phala TEE enclaves and are accessed by their public endpoint URLs.
• Protocol API is open for read endpoints. Provisioning endpoints require valid NEAR account IDs.
• Ensue API requires an Authorization: Bearer {ENSUE_API_KEY} header on every request.

Conventions

All APIs return JSON. Timestamps are ISO 8601 strings. DID identifiers follow the did:key:z6Mk... format (Ed25519).

Error responses use the shape:

{
  "error": "Human-readable error message",
  "details": "Optional technical details"
}