For lean and budget-conscious teams

Predictable, prepaid pricing with no subscription commitment and no international card required — for teams that need to know exactly what an AI feature will cost before it ships.

If your team is optimizing hard on cost — because you're bootstrapped, because a subscription in a foreign currency is a real line item, or because you just don't want a bill that swings 3x month to month — the defaults matter more to you than they do to a well-funded team that can absorb surprises.

Why prepaid beats a subscription here

A subscription bets that your usage will be steady enough to justify a fixed monthly fee. Early-stage and cost-conscious teams rarely have steady usage — it's spiky, tied to a launch, a demo, a client project. Relixr runs on prepaid credits instead: you add what you can commit to, it's reserved before each request and settled to the real cost once the response comes back, and it never expires. You're never paying for a subscription tier you didn't use, and you're never surprised by a bill that assumed you would.

No card, no subscription, to get started

You don't need a card on file to try Relixr — see sign up. Add credits only when you actually need a model beyond the free community catalog, and top up with a card or mobile money, whichever is easier to get your hands on. Pricing displays in your local currency alongside USD, so you're comparing against a number that means something to you, not converting in your head every time.

Keeping the bill predictable as you grow

• Start on the cheapest model that works. See Choosing a model for a task — most tasks don't need a frontier model, and starting cheap is the easier default to walk back from than starting expensive.
• Set a spend ceiling on day one. A cap on your key means a bug in your own code fails a request instead of draining a balance you can't easily replace — see Setting spend controls.
• Read the per-request cost, not just the monthly total. Every response tells you exactly what it cost and which model handled it (see Headers & metadata) — enough to catch an expensive call before it becomes a pattern.
• One key, one integration, every provider. You're not paying to maintain four separate SDK integrations to keep your options open on price — see OpenAI compatibility.

See Relixr for solo developers if it's just you, or Relixr for platform teams once budget needs to be split across projects.