lbreeze

An API key for a model, on the bill you already have.

Add AI to your application without opening an account with another company, handing over another card, or discovering at the end of the month what it cost. Your own key, your own limits, your own invoice.

Talk to us about AI endpoints
# your key, your endpoint
curl https://ai.yourhost.com/v1/chat/completions \
-H "Authorization: Bearer sk-••••••••" \
-d '{"model":"…","messages":[…]}'
 
# over your rate limit
429 Too Many Requests
Retry-After: 2
 
# past your monthly cap
403 Forbidden
# not a 429 — retrying will not help

What you get

A key, a limit, and a bill you can check.

A key and an endpoint

Point your application at it and call it. Nothing to install, nothing to keep running, and no GPU to rent by the hour and forget about.

A monthly cap you set

The number you are not willing to go past. Beyond it the endpoint refuses the call rather than carrying on and billing you for it.

A rate limit that is yours

Your limit is your limit. Another customer having a busy day does not spend it.

It runs on our machines

The same estate as your hosting, in the same place, under the same agreement — rather than your customers’ text being sent to a third party you have not vetted.

On your existing invoice

One supplier, one renewal date, one bill. If you stop paying it suspends alongside everything else instead of becoming a separate problem.

Usage you can check

Every call is recorded individually, so the figure on your invoice is a sum of rows you can look at rather than a total to take on trust.

tenant Atenant Btenant Cgatewayyour keyyour quotasone runtimeper model, per nodesharedthe weights are the memory, so the runtime is shared —your key, your limits and your usage are not

The bits developers ask first

Short answers, no sales call.

Your key is stored as a hash

Only a SHA-256 of it is kept, compared in constant time. The key itself is not in our configuration, not on the machine serving you, and not in the logs.

A call we cannot measure is not billed

If usage cannot be read back from the engine it is recorded as unmetered rather than estimated. We would rather under-count than put an invented number on your invoice.

Shared runtime, private everything else

One model runtime serves every tenant on a node, because the weights are several gigabytes and identical. Your key, rate limit, cap and usage record are yours alone.

Managing it

Four things you will actually do.

Rotate the key

A new key works immediately and the old one stops. Useful when someone leaves, or a key ends up somewhere public.

Raise or lower the cap

Takes effect straight away. Lower it before a risky deploy if you want to.

Pause it

The key stops working and nothing is charged. Turn it back on when you want it.

Cancel it

The endpoint goes and nothing of yours stays behind on the machine.

Questions

Before you build on it.

Is my data used to train anything?

No. These are models serving requests, not a training pipeline. Your calls are metered and answered; they are not collected as a dataset.

Which models can I call?

It depends what the machines in your location are running, and it changes as we add capacity. Ask and we will tell you what is available where you are — rather than publish a list that is wrong in a month.

What does it cost?

You are charged on usage, against the cap you set. Tell us roughly what you are calling today and how much, and we will give you a real figure rather than a range.

Can I try it before committing?

Yes. Set a small cap and point something at it. The cap is the whole safety net — there is no way for it to cost more than the number you chose.

It sits with the rest of your hosting

Same panel and same bill as your websites, email, DNS, databases and machines.

See all hosting