-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0007: Unified Embedding API #13
base: main
Are you sure you want to change the base?
Conversation
proposals/0007-embedding-api
Outdated
|
||
#### User Request Schema for Embedding Route | ||
|
||
TBU |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking forward to see proposed unified requests/responses 👀 The remaining workflow should be fairly close to the chat API.
.... | ||
-0.0028842222, | ||
], | ||
"token_count": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have recently changed token_count
to token_usage
. I feel like this is a bit more explicit.
|
||
## Future Work | ||
|
||
- Could we abstract away the entire RAG architecture? A single endpoint that takes a chat message -> embeds -> text semantic search -> LLM -> response |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This actually sounds like an idea for another service that would use Glide to talk to LLMs while providing RAG related addition to Glide's workflows. @mkrueger12 what do you think? What would be MVP for such a service?
No description provided.