API compatibility
The requested target is a complete DarkSeek service with the developer experience of DeepSeek. A matching UI, parser flag, or forwarding route is not proof of full behavioral compatibility.
| Feature / route | Current evidence | Remaining gate |
|---|---|---|
| Model enumeration GET /v1/models | Verified in isolated Go tests | Public TLS and extended capability metadata pending |
| Text chat + SSE POST /v1/chat/completions | Real native/Go inference verified | External production, load and recovery pending |
| Responses protocol POST /v1/responses | Forwarding route only | Exact protocol and event lifecycle tests required |
| Anthropic Messages Not implemented | Parity backlog | Protocol adapter, tools, thinking and event tests |
| FIM completion Not certified | Parity backlog | Suffix/prefix semantics and tokenizer tests |
| Tools + reasoning controls Chat protocol fields | Runtime parsers exist; not certified | Agent workflow and parameter conformance tests |
| Balance + billing Not implemented | No prices or balances invented | Commercial policy, durable accounting and payment integration |
| Files Not implemented | Parity backlog | Durable storage, tenant isolation, retention and quotas |
| Search + fetch Not implemented | Parity backlog | Search service, safe fetching, SSRF controls and spend policy |
| Context caching + usage Not certified as customer contract | Runtime cache metrics observed | Accurate per-tenant usage and cache metadata |
| Web accounts + API keys Better Auth/D1 + operator keys | Foundations present; not integrated | D1, verified account lifecycle, key ownership and durable quotas |
These statuses describe the implementation and bounded tests in the local workspace, not a publicly deployed production service. Do not use the live DeepSeek service’s prices, user balances, capability promises or model catalogue as DarkSeek facts.