Integrations · Agent frameworks
Build production agents on Run BiOS.
LangChain, LlamaIndex, CrewAI, PydanticAI, Strands Agents — the orchestration frameworks all accept an OpenAI-compatible endpoint. Point one at Run BiOS and your agents run on the same API, serverless or on your own dedicated deployment.
from openai import OpenAI
client = OpenAI(
base_url="https://api.runbios.ai/v1",
api_key="sk-bios-...",
)
resp = client.chat.completions.create(
model="deepseek-v4-flash", # any served model id
messages=[{"role": "user", "content": "Summarize my inbox"}],
)Three values — base URL, API key, model id. Every framework below takes the same three, just in its own config.
Frameworks
Where the three values go
Each framework keeps its own config format — the values never change. Exact file paths vary between versions; the pattern below is the one every version accepts.
LangChain
Build LLM applications with powerful orchestration and tool integration.
ChatOpenAI — set base_url and api_key on the model, pick any served model id.
LlamaIndex
Efficient data retrieval and document indexing for LLM-based agents.
OpenAI LLM — set api_base and api_key, then index and query with any served model.
CrewAI
Orchestrate collaborative multi-agent systems for complex tasks.
LLM config — base_url and api_key per agent, or once for the whole crew.
PydanticAI
Type-safe AI agent development with Pydantic validation.
OpenAIModel — pass base_url and api_key to the model constructor.
Strands Agents
Modern agent orchestration with seamless OpenAI-compatible integration.
Model provider config — an OpenAI-compatible endpoint with your key and model id.
AWS AgentCore
A managed runtime for deploying production AI agents, with bring-your-own model providers.
Model provider settings in the AgentCore console — OpenAI-compatible endpoints supported.
Not listed? If it accepts an OpenAI-compatible endpoint, the same three values apply. Per-framework walkthroughs are being verified and will be linked here as they pass.
Why Run BiOS
The framework builds the agent. Run BiOS serves the model.
The framework keeps its loop
Memory, tools, and orchestration stay in the framework you already chose. Run BiOS supplies the model behind one OpenAI-compatible endpoint — nothing else changes.
Agents burn tokens. Pay per token.
An always-on agent is a high-volume workload. Serverless inference bills per million tokens at the model library rates — no seat licenses, no minimums.
Your weights, the same three lines.
Fine-tune a model on dedicated GPUs and serve it on a dedicated endpoint behind the same API. The framework config does not change — only the model id does.
Questions teams ask before switching
Which orchestration frameworks work with Run BiOS?+
Any framework that accepts an OpenAI-compatible endpoint: LangChain, LlamaIndex, CrewAI, PydanticAI, Strands Agents, AWS AgentCore, and the OpenAI SDKs themselves. The integration surface is three values — base URL, API key, model id.
Do I need to change my framework code?+
No. You change where the framework looks, not what it does: set the base URL to the Run BiOS endpoint, use your API key, and pick a served model id. The framework keeps its own loop, tools, and memory.
Can my framework use a model I fine-tuned on Run BiOS?+
Yes. A finished checkpoint can go onto a dedicated endpoint behind the same OpenAI-compatible API. The framework config is identical — only the model id changes, and the weights behind it are yours.
How is framework traffic billed?+
Per million tokens, at the same input and output rates published in the model library. There are no per-seat or per-agent fees, and cached input is cheaper where the model offers it.
Point your framework at Run BiOS tonight.
New accounts start with a $10 free credit — enough to run an agent for days and see the three-value setup for yourself.
Per-million-token billing · Zero data retention · Your weights stay yours