DeepSeek opens its app APIs and adds chat-history import to an open-source client
Developers can reuse DeepSeek’s search, file and voice services in their own interfaces. The demo can run locally, but its model and tool calls still go to the API.
DeepSeek is giving developers more than a model to put behind a chat box. On November 13, it opened the application services used by its own chat product and published a demonstration client that can import existing DeepSeek conversations. The company says developers can use the package to recreate the app’s experience. The practical attraction is being able to change the interface without starting again with an empty conversation history or rebuilding every supporting tool.
A model connection alone leaves a substantial integration job. An application still needs to find information, read documents and pass useful results into the conversation. DeepSeek now handles those connections on its servers when developers enable the appropriate options. The bundled conversation features are available with V4.1-Flash through three common API formats. It is a little like being offered a restaurant’s working kitchen rather than just its best cook: a developer can concentrate on the menu and front room while reusing the machinery behind them.
The accompanying open-source client makes that proposition tangible. Its documentation describes a static web application that needs no separate application backend. A downloaded copy can be opened in a local browser, with an API key supplied in settings to authorize service calls. Conversations, attachments and settings are kept in that browser. Messages, file uploads and speech requests still send relevant content to the configured API service, however. Hosting the interface on a laptop does not turn it into an offline model.
History portability comes with details worth checking before a move. The client can import a DeepSeek export and let the user continue those conversations. After confirmation, an import replaces the client’s existing local conversations and attachments instead of adding another batch alongside them. Its export format includes conversations and locally available original images, but not API keys, settings or original non-image attachments. Users moving their work should keep a backup of existing chats and retain important source documents separately.
The tools also have their own bill. On November 15, DeepSeek’s Chinese pricing page listed search and web fetching at 5 yuan per thousand calls each, and file parsing or optical character recognition at 1.5 yuan per thousand pages. Model token charges are additional. Smaller teams gain a ready-made connection between a model and its supporting services, while users get another place to carry on an existing conversation. Public-facing applications still need content management: DeepSeek requires developers to enable safety checks and retain responsibility for reviewing their services. The package supplies building blocks rather than a finished public product that can simply be left unattended.
Original announcement date: November 13, 2026.
Share this article
What do you think of this story?
Anonymous feedback, up to 5 reactions per article.
Reader comments
Comment without signing in, or sign in to display your member name.
Discuss the technology and the story. Hate, politics and war, threats, abuse, personal accusations, sexual content, ads, links and personal information are not allowed.
No comments yet. Be the first to share.