Build with Enclave42 model APIs.

Quickstart

Create an API key from the dashboard, assign it to an allowed model, then call the chat completions endpoint from your backend.

curl https://api.enclave42.com/v1/chat/completions \
  -H "Authorization: Bearer <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen3-32b-tee",
    "messages": [
      {
        "role": "user",
        "content": "Reply with a short product summary."
      }
    ]
  }'

Authentication

API requests require a bearer token. Keep your API key server-side and never expose it in a browser, mobile app, public repository, or client-side bundle.

Chat completions

The primary endpoint follows an OpenAI-compatible chat completions format.

Example response

{
  "id": "chatcmpl_...",
  "object": "chat.completion",
  "model": "qwen3-32b-tee",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Here is a concise product summary..."
      },
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 24,
    "completion_tokens": 18,
    "total_tokens": 42
  }
}

Models

Use the exact technical Model ID displayed in the Models page or API Keys page. Model access depends on the customer plan and the model assigned to the API key.

Wallet billing

Subscription controls platform access and model tiers. Wallet balance pays for actual inference consumption. Each successful request creates a usage record and a wallet debit.

Error responses