DARKSEEK API DOCS

A familiar API.
A new place to build.

Build with DarkSeek using a chat-completions-compatible interface. These guides describe the current implementation and distinguish it from features still awaiting acceptance.

Your first API call

Set DARKSEEK_BASE_URL to the HTTPS origin supplied with your DarkSeek access, with no trailing /v1. Set DARKSEEK_API_KEY to your issued key in a server-side environment. A public production API origin is not yet verified; these examples do not establish availability.

curl "$DARKSEEK_BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer $DARKSEEK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"darkseek-v4.1","messages":[{"role":"user","content":"Hello DarkSeek"}],"max_tokens":256,"stream":false}'

SDK examples use the chat-completions request schema. Package-specific SDK integration is a separate verification gate; do not expose these keys in frontend code.

Stream a response

Set stream: true. Read choices[0].delta.content from SSE data events until [DONE]. An error event or incomplete stream is not successful completion. Abort the HTTP request to cancel generation.

Chat completions reference →

Models, limits & errors

The configured model alias is darkseek-v4.1. Query GET /v1/models with a valid key for the deployed registry and output ceiling. Do not infer context length, vision or tools from a model name.

Use max_tokens to bound output. Per-key rate and concurrency limits are deployment policy. On HTTP 429, respect Retry-After; avoid unlimited automatic retries. Keep X-Request-ID for support without sharing keys or prompts.

Error and retry reference →

Access & accounts

Better Auth and Drizzle/D1 provide the account foundation. Operator-issued API keys currently gate the isolated Go service. Account-linked self-service keys, email verification/recovery, durable usage metering and billing remain production launch gates.

Full protocol and product compatibility matrix →

Privacy & data

Chat keys and conversations stay in tab memory and clear on reload. Requests and generated responses pass through the DarkSeek service. The Go gateway does not log prompt bodies or Authorization headers. Backend retention, data-location terms and incident response must be reviewed before sensitive data or general onboarding.