Core
Core Reference
Public exports from @anvia/core and its subpaths.
@anvia/core is the provider-neutral runtime package. The root entry point re-exports the public APIs from each core subpath.
Import Paths
| Import path | Area |
|---|---|
@anvia/core | Root export that re-exports the public core subpaths |
@anvia/core/agent | Agents, prompt requests, hooks, approvals, and run events |
@anvia/core/completion | Provider-facing completion messages, requests, responses, usage, and model contracts |
@anvia/core/tool | Tool definitions, registries, tool sets, serialization, and tool errors |
@anvia/core/pipeline | Typed pipelines and batch execution |
@anvia/core/extractor | Structured extraction helpers |
@anvia/core/embeddings | Embedding models, documents, and vector math |
@anvia/core/vector-store | In-memory vector store, vector filters, and vector search tools |
@anvia/core/mcp | MCP connection helpers and normalized MCP types |
@anvia/core/observability | Observer interfaces, trace options, and score contracts |
@anvia/core/skills | Skill loading, local skill discovery, validation, and generated skill tools |
@anvia/core/streaming | Conversion from async iterables to web ReadableStream |
Root Export Notes
The root @anvia/core export is the convenient application import path. Subpaths are useful when provider packages or libraries need tighter import boundaries.
import { AgentBuilder, createTool, Message, PipelineBuilder } from "@anvia/core";
import type { CompletionModel } from "@anvia/core/completion";For workflow guidance, start with Core Concepts.