Repository navigation
VLLM
build_client / build_async_client — two thin helpers that point the standard, unmodified
openai Python client at your engine's OpenAI-compatible /v1/chat/completions and
/v1/responses surface, resolving the right base_url/api_key.
Direction, stated plainly: this package is vLLM (or any OpenAI-client-shaped consumer) calling into Algenta — never Algenta calling out to a vLLM-hosted model. The reverse direction isn't buildable in this repository (it would mean engine-side logic, which the no-engine-dependency gate forbids).
pip install vllm-algentaOne dependency: the real openai client (>=1.50).
import os
from vllm_algenta.client import build_client
client = build_client(
base_url="http://localhost:8000", # your engine's bare HTTP origin — no /mcp suffix
api_key=os.environ["ALGENTA_API_KEY"], # required — raises immediately if unset
)
resp = client.chat.completions.create(
model="text.tokenizer",
messages=[{"role": "user", "content": "Summarize this quarter's decision log."}],
)
print(resp.choices[0].message.content)base_url resolves from base_url= → ALGENTA_BASE_URL → http://localhost:8000; the package
appends /v1 itself. api_key resolves from api_key= or ALGENTA_API_KEY with no fallback
— every route on the engine's LLM API requires an authenticated, org-bound caller.
Not applicable — this package exposes no MCP tools. The tool-profile contract governs the engine's MCP surface; this package speaks to the separate OpenAI-compatible HTTP API.
-
Capability status is documented honestly and re-verified — the package README's table says
what works against the served API today: basic chat completions work;
finish_reasonand tool calling work but are model-dependent (the zero-config defaulttext.tokenizerdeterministically returns"stop"and loudly rejectstools=with422 model_capability_unsupported); streaming is synthetic post-hoc rechunking by default, and streaming + an actual tool call is refused. Known gap: the package's/v1/responsescoverage models a narrower shape than the real engine now supports (tools,previous_response_id, typed input arrays) — tracked, and documented in the README rather than implied otherwise. -
Tests: real FastAPI stub on a real
uvicornsocket, driven with the realopenaiclient —uv run pytest vllm-algenta -v.
Full reference: package README (full capability table with evidence, auth rationale, base-URL suffix gotcha).
thyn-ai/algenta-integrations · Apache-2.0 · The Algenta engine is separate, closed-source software — these packages are ordinary Python and TypeScript talking to its public HTTP/MCP APIs. · Support · Security · Discord
Start here
Framework guides
- LangChain
- LlamaIndex
- Pydantic AI
- MS Agent Framework
- Haystack
- LiteLLM
- Ray Serve
- vLLM
- Vercel AI SDK
- n8n
Project