One key for retrieval and generation
Create embeddings and call the answer model through one identity, usage ledger and prepaid balance.
Use one platform for vectorizing knowledge, retrieving relevant context and generating grounded answers—with measured usage across the full pipeline.
POST /v1/embeddingsAIx keeps identity, integration and measured billing consistent while your workload uses the model best suited to the job.
Create embeddings and call the answer model through one identity, usage ledger and prepaid balance.
Use efficient embedding and chat models for background indexing, then reserve premium reasoning for difficult queries.
Change embedding or answer models independently without replacing the surrounding API integration.
Use these as practical starting points, then evaluate quality, latency and unit economics against your own traffic.
Split source documents into useful semantic units and store their vectors with source metadata.
Embed the user query, fetch the closest passages and apply filters or reranking before generation.
Send only the strongest context to the chat model and require answers to reference the supplied sources.
POST /v1/embeddingsfrom openai import OpenAI
client = OpenAI(
base_url="https://api.aix.theaimart.co/v1",
api_key="$AIX_KEY",
)
vector = client.embeddings.create(
model="BAAI/bge-large-en-v1.5",
input="How does measured billing work?",
).data[0].embeddingBuild a complete RAG pipeline →Yes. Use the same key for embeddings and chat generation, with usage recorded in one AIx ledger.
Choose a model based on language, retrieval quality, vector size and cost. BGE Large EN v1.5 is a strong general-purpose English starting point.
The API processes request content but AIx does not store prompts or model responses. Your application owns document storage and vector indexing.
One key. One API contract. The AIx model network behind it.