Reflex: retrieval built for recurring documents
Reflex reuses semantic embeddings and lexical evidence to deliver competitive top-10 ranking, a 3.21x faster warm path and lower recurring-corpus costs.
Read postAIVAX brings models, retrieval and tools into one OpenAI-compatible operating layer, so behavior can evolve without losing the trail of what happened.
Knowledge matters when its path into an answer remains visible.
From the blog
Reflex reuses semantic embeddings and lexical evidence to deliver competitive top-10 ranking, a 3.21x faster warm path and lower recurring-corpus costs.
Read postInside one request
Keep the client simple. Let a gateway carry the instructions, knowledge, tools and policy that should be shared across applications.
See the request anatomyPOST /v1/chat/completions
model · instructions · RAG · tools · moderation
choices[] · usage · generation_context
Compose knowledge, model behavior and tools behind one OpenAI-compatible call. Each capability stays reusable, inspectable and shared.
RAG / 06 primitives
Enrich a gateway with retrieved context while keeping the client unchanged.
Regenerate indexed chunks and vectors when document content changes.
Send larger document sets through a bounded import pipeline.
List, filter, update and remove documents and indexed chunks.
Expose collection search to agents as generated MCP tools.
Refine retrieved candidates before they enter the model context.
Gateway / 09 primitives
Route one familiar call across integrated and external models.
Cover eligible model usage through plan-based reserve windows.
Extract, validate and retry malformed JSON against your schema.
Use provider-native or AIVAX-managed JSON Schema output.
Load specialized system instructions only when a request needs them.
Translate images, audio, video and files into text before inference.
Trim context and tool messages to fit the selected model.
Apply input and output checks as reusable gateway policy.
Load shared instructions from controlled remote sources.
Tools + providers / 05 primitives
Apply policy, enrichment and audit logic outside the prompt through authenticated HTTP hooks.
Attach server-side tools to the same request path.
Let models without native tool calling invoke functions.
Run shell tools inside isolated sandboxed environments.
Connect an external OpenAI-compatible provider through the gateway.
A shared path matters when every application can rely on it.
Field guide
Start with the question in front of you: knowledge, execution, model choice or cost.