Support deepseek V3 & R1

[impactCn]

The deepseek model cost reduces the ai model to a very low level. More and more people are using this open source model. I want to integrate it into spring ai so that more people can use this model directly.

[ricken07]

DeepSpeek is compatible with openAi sdk, you can directly use deepSeek models with Spring AI Open AI integration as for Groq you just need to change the base URL and search for its api key in the configuration, I have submitted this Pull Request to improve deepSeek support

[murphye]

Run in ollama as well. Llama distilled version of R1:

ollama run deepseek-r1:8b

[robbyzhaox]

It is stated in DeepSeek's api-docs that the API is compatible with OpanAI.

[mbetrifork]

Spring-ai might not be perfectly compatible with reasoning models in general, in the sense that the application may want to deal with reasoning/thinking tokens independently of the final response.

[markpollack]

I think we need to create a deepseek model module.

This commit 45421b1

added fields to the response of openai which are specific to deepseek. This sort of leakage is happening in multiple places from models that are a super-set of openai api.

There are a couple options on how to approach this.

1. We are having a RC1 next month, March 13. I am not sure if this work can realistically be done by then. It would be nice to have this model in spring-ai proper.
2. A more conservative option, that actually increases velocity, as you would be in full control of the repository, is to have the deepseek model development can take place as part of the new spring-ai-community organization. You can read more about it here - https://github.com/spring-ai-community/community/wiki Then when it is mature , it could be moved into spring-ai.

I think option 2 is more realistic, but let me know. @mxsl-gr Thoughts?

[mxsl-gr]

hi, @markpollack

Option 2 does sound like the safer path. That said, I believe the timing might still work out. I should have some time over the next two weeks and will try updating the implementation based on the previous PR: #702.

If the updates bring it to a ready state before the RC1 deadline, we could merge with including it in Spring AI. Otherwise, I’m happy to migrate the work to the Spring AI Community organization and continue development there until it's ready to be promoted back into the main project.

[apappascs]

Hi @mxsl-gr, I just saw the latest messages and the PR: #2192.

Looks like you’re already working on this and the PR needs a few changes. Just wanted to check so we don’t both work on the same thing. If you’re short on time, I’m happy to help.

[mxsl-gr]

Hi @mxsl-gr, I just saw the latest messages and the PR: #2192.

Looks like you’re already working on this and the PR needs a few changes. Just wanted to check so we don’t both work on the same thing. If you’re short on time, I’m happy to help.

Hi @apappascs , Sorry for the late reply, and thanks for reaching out!

I'd be happy to collaborate. This PR is mainly based on some earlier work I did in a previous PR, so I’m planning to follow through and make the necessary updates in the next few days when I get a bit of time.

Really appreciate the offer—I'll let you know if I could use a hand. Thanks again!