Skip to main content

animuz-core

Core shared utilities for Animuz RAG (Retrieval-Augmented Generation) system.

Features

  • Unified RAG API: 3-knob interface (prompt, llm, tools) for chat, ingestion, and retrieval
  • LLM Clients: OpenAI (Responses API + Chat Completions), Anthropic Claude, Ollama
  • Tool System: @tool decorator, qdrant_retriever() factory, MCP server support
  • RAG Pipelines: Simple and Agentic RAG implementations (lower-level building blocks)
  • Vector Database: Qdrant integration with hybrid search (dense + sparse)
  • Embedding Clients: Multiple providers (local server, Modal, S3/SageMaker)
  • Document Ingestion: Azure Document Intelligence, Unstructured, PDF extraction, structured text parsing
  • CloudWatch Logging: Structured JSON logging with watchtower

Requirements

  • Python >= 3.10

Installation

Install the core package (minimal dependencies only):

pip install animuz-core

Then install only the extras you need:

# Single extra
pip install animuz-core[openai]

# Multiple extras
pip install animuz-core[openai,qdrant,aws]

# Everything
pip install animuz-core[all]

Works with uv too:

uv pip install animuz-core[openai,qdrant]

Available Extras

Extra What it installs Use when you need
openai openai OpenAI GPT models
anthropic anthropic Anthropic Claude models
ollama ollama Local LLMs via Ollama
qdrant qdrant-client Qdrant vector database
aws boto3, aiobotocore, watchtower, sagemaker S3, SageMaker embeddings, CloudWatch logging
azure azure-ai-documentintelligence Azure Document Intelligence for PDF ingestion
ingest unstructured-client, PyMuPDF Document parsing (Unstructured API, PDF extraction)
fastapi fastapi Streaming SSE endpoints
all All of the above Everything
dev all + pytest, black, ruff, mypy Development and testing

The opt-in live V31MCPTools signed routes need boto3 at execution time. Install the aws extra (for example, animuz-core[openai,aws]) in a serving adapter that uses them. Fixture-only offline turns do not need AWS credentials.

Usage

The RAG class is the main entry point. It has 3 knobs:

  • prompt — callable (team_id, assistant_id) -> dict that fetches an assistant config
  • llm — model name string (provider auto-detected: "gpt-*" → OpenAI, "claude-*" → Anthropic)
  • tools — list[ToolSpec] for local tools, MCP(url=...) for MCP server, or None for plain chat
from animuz_core import RAG, qdrant_retriever, tool

# Define how to fetch the assistant config
def my_fetcher(team_id, assistant_id):
    return {"prompt": "You are a helpful assistant.", "model": "gpt-4o-mini"}

# Create RAG with local retriever tool
rag = RAG(
    prompt=my_fetcher,
    llm="gpt-4o-mini",
    tools=[
        qdrant_retriever(host="localhost", port=6333, collection="animuz"),
    ],
)

# Chat (returns frontend-ready output)
output = await rag.chat("team1", "asst1", [{"role": "user", "content": "Hello"}])

# Ingest a document
await rag.add_doc("docs/intro.md", user_chat_id="team1|asst1")

# Retrieve documents
texts, points = await rag.retrieve("what is this?", user_chat_id="team1|asst1")

With MCP tools (Lambda / cloud)

from animuz_core import RAG, MCP

rag = RAG(
    prompt=ddb_fetcher,
    llm="gpt-4o-mini",
    tools=MCP(url=os.environ["MCP_URL"], api_key=os.environ.get("MCP_API_KEY")),
)
output = await rag.chat(team_id, assistant_id, messages, user_context=ctx)

Plain chat (no tools)

rag = RAG(prompt=my_fetcher, llm="gpt-4o-mini")
output = await rag.chat(team_id, assistant_id, messages)

Custom OpenAI base URL (proxy / gateway)

Route OpenAI API calls through a proxy or API gateway by passing base_url:

rag = RAG(
    prompt=my_fetcher,
    llm="gpt-4o-mini",
    base_url="https://your-proxy.example.com/openai/v1",
    tools=[qdrant_retriever(...)],
)

When omitted, the default OpenAI endpoint (api.openai.com) is used.

Custom tools with @tool decorator

from animuz_core import RAG, tool, qdrant_retriever

@tool(description="Get weather for a city")
async def weather(city: str) -> str:
    return await fetch_weather(city)

rag = RAG(
    prompt=my_fetcher,
    llm="gpt-4o-mini",
    tools=[qdrant_retriever(...), weather],
)

Lower-level APIs

LLM Clients

from animuz_core import OpenAIAgentClientResponses

# OpenAI Responses API agent with tool loop (recommended for production)
agent = OpenAIAgentClientResponses(user_chat_id="tenant-123", tools=tool_dict, model="gpt-4o-mini")
result = await agent.get_reply_frontend(messages, system_prompt)

# With a custom base URL (proxy / gateway)
agent = OpenAIAgentClientResponses(model="gpt-4o-mini", base_url="https://your-proxy.example.com/openai/v1")

RAG Pipelines

from animuz_core import SimpleRAG

# Simple RAG — always retrieves then generates
pipeline = SimpleRAG(
    embedding_client=embedding_client,
    db_client=qdrant_client,
    LLM=llm_client,
)
await pipeline.add_doc("document.pdf", user_chat_id="tenant-123")
result = await pipeline.query("What is RAG?", user_chat_id="tenant-123")

Vector Database

from animuz_core import QdrantDBClient

client = QdrantDBClient(host="localhost", port=6333, collection_name="animuz")
results = await client.hybrid_search(dense_vec, indices, values, user_chat_id="tenant-123")

Embedding

from animuz_core import EmbeddingClient, ModalEmbeddingClient

# Local embedding server
client = EmbeddingClient(host="localhost", port=12081)
result = await client.get_embedding("Some text")

# Modal-hosted embeddings
client = ModalEmbeddingClient()
result = client.get_embedding("Some text")

Development

# Clone and install in editable mode with dev dependencies
git clone <repo-url>
cd animuz-core
pip install -e ".[dev]"

# Run tests
pytest tests/

# Run integration tests (requires external services + env vars)
pytest -m integration tests/integration/
pytest -m integration tests/integration/test_e2e_rag_wrapper_simple.py

# Format
black src/
ruff check src/

Rudi ChatV4 turn coordinator

animuz_core.rudi_v4.run_turn is the shared async event generator for a future ChatV4 serving adapter and offline evaluation. It assembles the opt-in V31 prompt, maps messages, and runs the streaming agent. The caller must supply an authenticated assistant snapshot or resolver, state coordinator, tool gateway, model client, model settings, and clock. The gateway owns action and unknown-tool policy. This package does not provide a replay endpoint or a customer-data reader.

The generator emits one done event only after the final assistant message and all tool calls have matching outputs. Core response.completed events mark model rounds; they do not complete the turn. A caller must still implement delivery, authorization, and durable state for its own serving environment.

Publishing to PyPI

  1. Bump the version in pyproject.toml and __init__.py.

  2. Build the package:

uv pip install --upgrade build
uv run python -m build
  1. (Optional) Verify the artifacts:
uv pip install --upgrade twine
uv run python -m twine check dist/*
  1. Upload to TestPyPI first:
uv run python -m twine upload -r testpypi dist/*
  1. Upload to PyPI:
uv run python -m twine upload dist/*

Notes:

  • Create a PyPI API token and set TWINE_USERNAME=__token__ and TWINE_PASSWORD=<your-token>.
  • If you upload to TestPyPI, install with pip install -i https://test.pypi.org/simple animuz-core to verify.

Integration Test Setup (Qdrant)

Use Docker Compose to run Qdrant locally:

docker compose -f docker-compose-qdrant.yml up -d qdrant

Then set the Qdrant env vars (example):

export QDRANT_HOST=localhost
export QDRANT_PORT=6333

Environment Variables

The package reads configuration from environment variables (loaded via python-dotenv):

Variable Used by
OPENAI_API_KEY OpenAI client
ANTHROPIC_API_KEY Anthropic client
QDRANT_HOST, QDRANT_PORT, QDRANT_COLLECTION_NAME Qdrant client
QDRANT_CLOUD_API_KEY Qdrant Cloud
EMBEDDING_HOST, EMBEDDING_PORT Embedding client
AZURE_DOCAI_KEY, AZURE_DOCAI_ENDPOINT Azure Document Intelligence
UNSTRUCTURED_ENDPOINT, UNSTRUCTURED_API_KEY Unstructured client
S3_BUCKET_NAME, S3_DOWNLOAD_DIR S3 operations
MCP_API_KEY MCP tool server

License

MIT

Metadata

Release files for animuz-core 0.1.17

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for animuz-core 0.1.17
File Size Uploaded Provenance Actions
animuz_core-0.1.17.tar.gz 81.2 kB Without provenance Details for animuz_core-0.1.17.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for animuz-core 0.1.17
File Interpreter ABI Platform Actions
animuz_core-0.1.17-py3-none-any.whl Python 3 none any Details for animuz_core-0.1.17-py3-none-any.whl

Total release size: 176.4 kB

Release files / animuz_core-0.1.17.tar.gz

Download URL animuz_core-0.1.17.tar.gz
Size 81.2 kB
Tags Source
SHA-256 checksum
How to use checksums
a235b7cdc0d04ca31e2cacc7f273595f83a5579cdf75d213c6f232334cd64bbe
BLAKE2b-256 checksum
How to use checksums
760eba735e24e135f7b9a0b1ac647114a1f6405f3f15e86a3fe530fe95b64dd5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.13

Release files / animuz_core-0.1.17-py3-none-any.whl

Download URL animuz_core-0.1.17-py3-none-any.whl
Size 95.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a9fea1dda98a09de0cd794e2fab5ab9dd73a1e9202c549ba3944440f04b28a24
BLAKE2b-256 checksum
How to use checksums
9efab989fa1ddee3ec587274ce74101d4b60729b6e0bd485ece68d33649b35c0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.13

Security for animuz-core 0.1.17

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page