Api Compatibility
Overview
Functional entry point for the API Compatibility section — endpoint map, unified auth, and how each compat layer is laid out
OpenAI Chat Completions
Use /v1/chat/completions with any OpenAI SDK — streaming, tool calling, and the Bodhi-specific model resolution rules
OpenAI Responses
/v1/responses async polling for reasoning and long-running tasks — pure pass-through to upstream providers, with strict ApiFormat rules
OpenAI Embeddings
Use /v1/embeddings against local or remote embedding models with the standard OpenAI SDK
Anthropic Messages
Use the Anthropic Messages API against Bodhi — header rewriting, model resolution, streaming, and the API-key vs Anthropic-OAuth split
Gemini
Use the Google Gemini /v1beta/* surface against Bodhi — header rewriting, action dispatch, streaming, and embeddings
Ollama (deprecated)
/api/* compatibility for legacy Ollama clients — limited surface, kept for migration only
MCP Proxy
Use Bodhi as an authenticated MCP front door — the per-instance proxy at /bodhi/v1/apps/mcps/{id}/mcp, JSON-RPC over HTTP, and how upstream auth is hidden from your callers
Error Format
The error envelopes you can see — Bodhi-native, OpenAI-style, and the provider-shaped wrappers the Anthropic and Gemini compat layers return