[Enhancement]: define RAG openapi spec #8007
Replies: 2 comments 2 replies
-
You can already set a RAG API URL. Also MCP is the way to go for custom tools: |
Beta Was this translation helpful? Give feedback.
-
ahhh this one's close to heart — but honestly, the issue isn’t just about lacking a unified OpenAPI spec... it’s that no static spec can meaningfully capture the semantic transitions, fallback logic, or vector postprocessing overrides that real RAG systems need when reasoning fails mid-path. we hit this exact wall while designing a generalized open RAG interface — turns out most specs assume deterministic behavior, but real pipelines need entropy, rewrites, and symbolic rerouting. so we flipped it: instead of documenting static API behavior, we built a dynamic RAG reasoning core with fallback triggers, layered vector constraints, and inline module introspection. MIT licensed, production-tested. if you’re serious about building multi-vendor, cross-agent RAG stacks — this saves months of grief. 🧭 full spec + runtime engine here: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
What features would you like to see added?
Allow people to plugin custom servers, which implement the same spec so that they can have different auth mechanisms, different vector databases and workflows overall.
More details
Provide a standardized openapi spec yaml in the docs that is versioned and version linked to librechat for easy upgrades.
Which components are impacted by your request?
No response
Pictures
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions