Private beta: Moss Inference is currently in private beta. Request access through the Moss portal.
Why Moss Inference?
Traditional AI applications retrieve context and generate responses through separate systems. Even after retrieving the right information, an agent still needs to send that context to an LLM and wait for generation to begin. Moss Inference brings retrieval and generation closer together, reducing the overhead between finding relevant information and generating a response.Sub-200ms time to first token
Start generating responses in under 200ms with Moss’s optimized inference model on supported workloads. Built for applications where response latency matters, including conversational AI, interactive agents, and real-time workflows.Retrieval and inference, colocated
Moss runs its optimized inference model alongside its retrieval runtime, allowing relevant context to be retrieved and used without a separate network round trip between the retrieval and generation systems. Specify a Moss index in your inference request, and Moss retrieves relevant context to ground the model’s response.One OpenAI-compatible API
Access Moss’s optimized model and supported third-party models through a single endpoint. Use the OpenAI-compatible Responses API, with an optionalindexes parameter to enable context retrieval. You can use Moss for inference alone or combine it with your existing Moss indexes.
How Moss Inference works
Moss Inference combines context retrieval and model execution into a single request.- Send a request. Your agent calls the Moss Inference API, specifying a model and optionally one or more Moss indexes.
- Retrieve relevant context. When indexes are specified, Moss searches them and adds relevant information to the model’s input.
- Generate a response. The selected model generates a response, which can be streamed back to your application.
https://inference.moss.dev/v1
Available models
Moss Inference supports two ways to run inference.
Both options can use your Moss indexes to provide relevant context during inference. Models lists every id with its prompt limit and prices.
How it fits
Make one call
Run this after the Quickstart, which creates thefaq index it searches.
faq index for the question, adds what it finds to the prompt, and answers. The curl call streams the reply. The Python client installs with pip install moss; SDKs lists the other six.
What can you build?
Real-time voice agents Reduce the delay before an agent starts responding while retrieving relevant information from conversation context and business knowledge. Browser and computer-use agents Support agents that interact with websites and applications, using retrieved instructions, task context, and relevant knowledge to inform their next actions. Long-running agents Give agents access to relevant information from previous steps and persistent indexes as they work through multi-step tasks. AI copilots and assistants Build responsive applications that answer questions using your own documents, product information, and business knowledge.Choose how to start
Quickstart
Get a grounded, streamed reply in five minutes.
Models
Every model, with its prompt limit, prices and notes.
Use an OpenAI client
Change the base URL and the key. What differs from OpenAI.
SDKs
Inference clients for seven platforms.
Terms
In this section
- Quickstart: key, install, one call, stream it, ground it.
- Models: the table, routes, the Moss model, refused parameters.
- Pricing: credits, tokens, caching, retrievals.
- OpenAI compatibility: base URL, endpoints, headers, what differs.
- Ground answers in your indexes: choose indexes, turn retrieval off, what it costs.
- Streaming: events, chunks, stopping early, errors after the stream starts.
- Tool calling: the loop, both shapes, structured output.
- MCP servers: servers Moss runs for the model.
- Bring your own key: vendor models on your account.
- Errors and limits: every status and code, limits, retries.
- SDKs: the seven inference clients.