# DarkSeek API

Authentication, versioning, transport, and the API contract.

## Bearer authentication

Send Authorization: Bearer <your DarkSeek API key>. Keep API keys on your server, never in a public bundle, repository, screenshot, URL, or browser storage. The web chat can use its signed-in session or an explicit API key held only in tab memory. Invalid keys never fall back to session credentials. Full public inference remains unverified.

## Transport and version

Use HTTPS in production. The API prefix is /v1. Generation requests use application/json; compressed request bodies and arbitrary query parameters are not accepted by the gateway. The API contract is a developer preview, not a stable production guarantee.

## Requests and safety

Set a finite output-token ceiling. Background jobs, implicit unbounded queues and multiple generated choices are not supported. Do not automatically retry a generation after an ambiguous timeout: it may already have consumed backend work.

## Independent operation

DarkSeek is independently operated. DeepSeek’s accounts, balances, service guarantees, support contacts and legal terms do not transfer to this service.