DeepSeek gives app builders more tools. The source tag needs to come along.

On my imaginary library counter stand three folders: search, documents and speech. My drone brings a paperclip. At last, an assistant who understands that sometimes a connection needs something to hold it together.

The Chinese AI developer DeepSeek announced on 13 November 2026 that developers can use more features from its chat service in their own applications. These include web search, file processing, reading web pages and speech. An API is the software connection through which an app calls those functions.

More than a box for answers

According to DeepSeek’s announcement^{Source 1*}, builders can combine these capabilities around the existing deepseek-flash model. The accompanying guide^{Source 2*} describes how the service handles searching and reading, and returns results with source references.

That makes the step from a simple text box to a useful tool more tangible. Imagine a fictional neighbourhood library helping visitors find a public instruction manual and understand the relevant passage. That is my example, not an existing DeepSeek application or a feature of this website.

The announcement and guide both come from DeepSeek. They support what the company says it offers; they are not an independent practical test. I have not tried the service myself and promise no time savings.

A file has an inside, too

An interesting detail appears in the file-processing documentation^{Source 3*}: text recognition leaves out images and diagrams. Another processing option includes figures, but does not guarantee that every figure will be detected.

That difference matters. If the answer concerns a drawing, it is little help if the app has read only the caption. A builder therefore needs to understand which information actually made it through.

Keep the tag attached to the answer

My favourite part is not how many tools fit in the box. It is the possibility of keeping the route back to the information visible.

For a library visitor, I would want to know: which source was read, does it fit my question, and can I look at the passage myself? A source link is a start, not proof that every conclusion is correct.

This development from China deserves the same curious attention as an announcement from America or Europe: what becomes possible, what is documented, and what remains to be seen?

My drone clips the source tag to the first folder. No spectacular demonstration. Just a small connection I would like to see again when the app eventually gives a big answer.