onrup

Integrations

Mostly, it is a base URL.

How do integrations work?

Serving implements the OpenAI chat-completions shape, so pointing an existing client at a fine-tuned model means changing a base URL and a key. That makes most of these pages short. What each one adds is the thing that specifically catches people out with that client — and where there is nothing, it says so.

Why there is so little to configure

A deployment serves the OpenAI chat-completions shape, so any client that already speaks it works by pointing at a different base URL with a different key. Requests, responses, streaming chunks and tool-call objects are the same structures, which means an application built against one provider moves to another without a rewrite.

That portability is deliberate and it cuts both ways: it is exactly as easy to move away from us as it is to move to us. We think a product that has to trap you is not a product worth building, and an integration layer that is a base URL is the cheapest possible proof of that.

Two things recur across these pages and are worth knowing before you start. Set temperature explicitly for anything structured — the default is not zero, and a classifier left at the default will occasionally invent. And raise your client's timeout if the endpoint can scale to zero, because a cold start is a slow first request rather than a failure, and a short timeout turns it into one.

SDKs and HTTP

Frameworks

Tooling

Model hubs

Start with the free tier

A magic link creates your account, your tenant and your first API key. No card until you ask for compute.