For solo developers
One key, sane defaults, and a bill you can predict — the setup for a single developer building on Relixr.
You don't need routing rules, guardrail policies, or key scopes on day one. You need one key that works and a bill that doesn't surprise you.
The five-minute setup
- Create an API key — the default inference key, no scopes to configure.
- Make a request with the OpenAI SDK, or pick a framework guide if you're using LangChain or the Vercel AI SDK.
- Set a monthly spend ceiling on the key so an infinite loop in your own code can't run past what you're willing to pay.
- Check Supported models once — pick one cheap default and one stronger fallback, rather than hardcoding a single model id everywhere.
Tip
Skip routing rules and guardrail policies until you actually have a second model or a real user base. They're there when you need them — see Model routing and Guardrails — but they're not required to ship.
What to revisit as you grow
- Moving from one model to two → Choosing a model for a task.
- Adding a background job or bot → treat it as its own key from day one, see Agent fleet on Relixr.
- Someone else joins the project → API key scopes before you share credentials.
Was this helpful?
Still stuck? Help center · Doctor