What capabilities does Anvia provide?
Anvia provides runtime primitives for model calls and the application behavior around them. Capabilities are split across Core, provider packages, infrastructure adapters, and optional product surfaces.
| Need | Anvia surface |
|---|---|
| One model request | Completions |
| Reusable multi-turn behavior | Agents |
| Application actions | Tools |
| Typed model data | Structured output |
| Conversations across requests | Memory |
| Document retrieval | Knowledges |
| Explicit multi-stage workflows | Pipelines |
| Incremental responses | Streaming |
| Images, audio, transcription, and OCR | Models |
| External MCP tools | MCP |
| Local inspection | Studio |
| Production observability and evaluation | Lens |
Availability is not uniform across every provider and runtime. A package implementing completion models may not implement embeddings, images, audio, OCR, or model listing. Tool-call semantics and structured-output support can also differ by model.
Use the provider capability matrix for model-facing support and the package feature matrix for package-level compatibility. Check each package's API reference for exact public exports rather than assuming a capability from its name.