Any library that supports OpenAI’s REST API works with RunInfra. Point it atDocumentation Index
Fetch the complete documentation index at: https://runinfra.ai/docs/llms.txt
Use this file to discover all available pages before exploring further.
https://api.runinfra.ai/v1 with your RunInfra API key and it behaves like OpenAI for every endpoint RunInfra serves.
LangChain
ChatOpenAI(openai_api_base=..., openai_api_key=...) and you are done.LlamaIndex
Works as
OpenAI(api_base=..., api_key=...) for both LLM and embeddings.Vercel AI SDK
createOpenAI({ baseURL, apiKey }) in app/api/chat/route.ts.The one-line rule
What’s not in this section
- The OpenAI SDK itself is documented under OpenAI compatibility. This section is for higher-level libraries on top of it.
- Observability and MLOps (Langfuse, Helicone, Arize, Datadog) pick up RunInfra traffic transparently when configured against an OpenAI-compatible endpoint. Point their base URL at RunInfra.
- IDE extensions (editor assistants that call RunInfra directly) are not supported out of the box today. If your editor supports a custom OpenAI-compatible endpoint, the same base-URL + key swap works, but we have not verified any specific editor and don’t document one until we do.
Missing an integration?
If a library supports OpenAI’s REST API, it works today. If you need a first-party adapter or cookbook for something that isn’t here, open an issue atRightNow-AI/runinfra-docs.