The Proxy Endpoint serves as a straightforward way to enhance your existing LLM setup with RAG-Buddy capabilities.
{system_instructions}
in the template with your instructions.## ID:<unique_identifier> [Article Title and Content]
. Content can be multi-line.Helvia-RAG-Buddy-Cache-Control
header is essential for managing how RAG-Buddy’s cache is used, influencing both reading and writing operations.
no-cache
: The cache will not be used for reading, but it will be updated with the new response.no-store
: Responses will not be added to the cache.no-cache, no-store
: Both reading from and writing to the cache are disabled.Cache-Control Header Option | Read from Cache | Write to Cache |
---|---|---|
no-cache | No | Yes |
no-store | Yes | No |
no-cache, no-store | No | No |
(Header Omitted) | Yes | Yes |
no-cache
header, if your cache already contains the same question, the response associated to that question will be overwritten.no-store
header, the question/answer will not be stored in the cache which could lead to not receiving cache hits for your requests.Helvia-RAG-Buddy-Cache-Status
.None
or an empty string.completions.with_raw_response
method. See the example below for more on that.