Skip to content
darkseek
API REFERENCE · DRAFT 0.1

DarkSeek API

A JSON-over-HTTPS API for the DarkSeek inference service, with bounded streaming and a chat-completions-compatible interface.

Authentication

HTTPAuthorization: Bearer YOUR_DARKSEEK_API_KEY

Every model and generation request requires a customer API key. Keep it in a server-side environment variable. Do not put keys in query strings, browser bundles, shared screenshots, or analytics.

Base URL

Use the origin of a deployment with its production Go API binding connected, followed by /v1. A separate API hostname can point to the same Go ingress once DNS and TLS are configured. No public API origin is declared ready yet.

API version & compatibility

The currently verified contract is small text chat, streaming, model enumeration, authentication, admission and cancellation through the isolated Go gateway. Full DeepSeek protocol parity is a separate acceptance gate, including tool lifecycle, reasoning controls, Responses, Messages, FIM, files, search/fetch, caching metadata and balance semantics.

Errors and request identity

Errors use a JSON error object with type, code and message. Request IDs are returned in X-Request-ID. Once an SSE stream begins, failures are explicit error events or incomplete streams, never a fabricated successful completion.

Customer accounts & operations

Better Auth/Drizzle provide the web-account foundation. Operator-issued keys currently gate inference. Account-linked self-service keys, durable metering, spend control, credits, billing, policy pages and production support channels are not yet activated.

Service identity

DarkSeek is operated independently by SenkuLabs. DeepSeek API keys, account balances, pricing, legal registrations and support addresses do not transfer to DarkSeek.