DeepSeek Puts Its Whole App Stack Behind One API and Open-Sources the Web Client
One vendor now supplies the search, fetch, OCR, file-understanding, and speech stack that previously forced agent and RAG builders to juggle Alibaba Cloud, Zhipu, and Volcano Engine accounts, SDKs, and auth paths. DeepSeek's open-sourced chat-demo hands over working reference code for the tricky parts: signed link contexts, in-browser WAV assembly, and streaming PCM playback.
DeepSeek's family-bucket API release converts the full feature set of its consumer App and web client into server-side capabilities. Three protocols are supported: Anthropic Messages, OpenAI Responses, and OpenAI Chat Completions. Built-in tools handle web search, deep-thinking search, link reading, file upload, and content safety, while separate REST endpoints expose search, fetch, OCR, ASR, and TTS for direct use in agent pipelines.
An integration write-up from a RAG knowledge base project documents the practical edges. Built-in and custom tools cannot share one request, so a project with its own retrieval walks around the built-in web search and calls the standalone search and fetch endpoints instead. The Files API bills by page count but returns no page count, forcing local preprocessing with PDFBox and headless LibreOffice to block encrypted files and estimate token cost. The built-in link-reader returns page content encrypted in a signature field that the frontend must echo back next turn, and streaming TTS needs odd-byte alignment buffering to avoid noise. The swap also replaced Alibaba Cloud OCR, which had burned through 500+ yuan in a week.
The signature-based read-link protocol keeps fetched page content off the client side entirely, but any custom client must reproduce the exact signature-echo behavior or lose web context across turns.
Charging by page count while omitting page count from the response is a billing blind spot that forces every serious integration to pay for its own page-counting pipeline.
The ban on mixing built-in and custom tools in one request pushes agent builders toward the standalone endpoints, which lose the tight deep-thinking integration the built-in tool provides.
Consolidating search, OCR, and TTS under one vendor removes multi-platform account and SDK overhead, but it concentrates availability and pricing risk in DeepSeek.
The two comments converge on the practical benefits of a unified API while flagging a critical cost-accounting pitfall. The first comment argues that before choosing providers, the industry must reconcile token counting, cache billing, and retry charges, otherwise any cost comparison is meaningless; it advocates one gateway with a single key. The second comment values the convenience of a single API for small tools and specifically appreciates the OCR coordinate output for document parsing.
After DeepSeek opens up the whole family bucket, everyone's first reaction is to grab a few more models, but the real trouble on the integration side is the metrics: the same prompt, different providers' token counts can differ by 20-30%; cache hits are sometimes listed separately, sometimes counted into input; 429 retries still get billed by the upstream. If these aren't aligned first, the costs calculated from selection are all wrong. Our approach is one gateway, one Key to call all domestic providers, with details exported by business line, and it reconciles at month-end. Details via private message.
This wave is indeed practical. Previously OCR, search, speech had to integrate several providers, now one API can string them together, which saves a lot of effort for small tools. The detail that OCR returns coordinates is quite useful, and can avoid many pitfalls in document parsing.