One line of code change to move from Open AI to Astra Assistants API

datastax.com

18 points·prabhatjha··8 comments

Our startup has been building agents inside of a workspace for the past few months. We had our first version about nine months ago, and the UI looks almost identical to OpenAI's.

That said, it's going to be very interesting to see if one AI Agent platform becomes the standard, or if people end up having different AIs for different platforms.

On our end at least, we are planning to keep our agent builder, even if we end up using OpenAI on the backend. At the very least we will at least maintain the agency to utilize another platform if we want.

Nice. What kind of agents are you building? I am especially interested in your data requirements.

I’m not sure exactly what you mean by data requirements, but we’re using Lang chain and still calling to GPT on the backend.

We’re building agents that are a little bit less autonomous than what is popular right now, mostly using them as chat bots that can interface with a workspace or chained into a type of workflow. Basically everything in our workspace will be accessible to the agents.

I love this! It makes AI assistants more accessible and user-friendly. Reminds me of the "Twin Sparrows" story in Kai Fu Li's AI 2041 book.

What is that?

The blogpost mentioned that the list of endpoints will be kept up-to-date on GitHub. Where would I find the link to the repo please?

We will be publishing the github repo in the next couple of weeks. As you can imagine this is happening in real time and we want to cross check few things before we publish the repo.

I will reply to this thread once that has happened.

Thank you.

Wow, this adds a layer of vector search integration that OpenAI is missing.

Reply on news.ycombinator.com