Terms & Conditions

Section 02. 02What the service is# (permalink)

Korlogic is an API gateway. It exposes an OpenAI-compatible endpoint, meters what you use, bills it against a balance held on your key, and forwards each request to a third-party model provider that generates the actual response. It does not train, host or run models of its own.

There are two billing surfaces, and a key belongs to exactly one of them:

The technical detail — base URLs, authentication, supported models, error codes — is in the documentation, which forms part of these terms to the extent it describes how the service behaves.

Section 03. 03Your key is your account# (permalink)

There is no signup, no password and no email account. A key is issued to you by the operator, and that key is both your credential and your identity: sending it authenticates a request, and pasting it at /login signs you in. Anyone holding the key can do everything you can do.

The key is stored only as a SHA-256 hash. It cannot be read back to you by anyone, including the operator. A key that is lost is replaced, never recovered, and replacing it does not carry the old key’s balance across unless the operator moves it.

Each key carries settings the operator chooses and you cannot change:

• Billing mode — credit or token, fixed at creation. It determines which base URL the key answers on.
• Model allowlist — an optional list of model ids. When set, any other model is refused.
• Rate limit — a ceiling on requests per minute. Requests over it are refused before being forwarded, and are not billed.
• Expiry — an optional date, after which every request fails even if credit remains.
• Status — active or suspended. A suspended key can be resumed without being reissued.

Section 04. 04Looking after your key# (permalink)

You are responsible for your key and for everything done with it. Because possession is the whole of the authentication, usage made with your key is treated as your usage and is billed to your balance, whether or not you made it.

• Keep the key on a server. Anything shipped to a browser or a mobile app is public.
• Do not commit it to a repository, paste it into a support ticket, or send it over email.
• If it may have leaked, ask for it to be suspended and replaced immediately. Suspension takes effect on the next request.

Section 05. 05How you are charged# (permalink)

Credit is prepaid and consumed per request. Nothing is invoiced afterwards and nothing accrues as a debt: you buy a balance, and requests draw it down until it runs out.

How a request is priced

• Money is held and computed as integer micro-dollars, where one dollar is 1,000,000 micro-dollars. Prices are set per model as a rate per million tokens, for input and output separately.
• Each component of a request is rounded up to the nearest micro-dollar, so a billable request is never free. On a credit key the total is deducted from your balance; on a token key the actual input plus output tokens are deducted from your budget.
• Token counts are the ones the model provider reports for that request. They are not estimated by us and they are not re-derived.
• Rates are set by the operator and can change. The rate applied is the one in force when the request is settled.

Admission and holds

Before a request is forwarded, an estimate of its cost is held against your balance, and a request is only admitted if your spendable balance — the balance less anything currently held — covers it. The hold is released when the exchange finishes, whether it succeeded, failed or was abandoned, and you are then charged the real cost rather than the estimate.

What you are not charged for

• Requests refused before forwarding. An invalid, suspended or expired key, a model outside the allowlist, an exhausted balance, or a request over the rate limit. These never reach the provider and cost nothing.
• Failures at the provider. If the provider returns an error, the request is recorded at zero cost and your balance is untouched.
• Requests we cannot meter. If an exchange completes but no usage figures come back, it is recorded at zero cost rather than estimated. We do not charge for a request we cannot price.

Your usage ledger is visible to you at any time through the usage checker or your dashboard, with per-request model, token counts and cost. If a charge looks wrong, raise it — there is a record of every request, and it can be checked.

Section 06. 06Buying credit# (permalink)

Credit is bought at /billing or from your dashboard. Which payment methods are available is the operator’s choice; the checkout shows the ones currently enabled, along with any minimum and maximum order amount.

Before you pay, the quote shows the full breakdown:

• the base amount you asked for;
• any surcharge the operator applies to that payment method;
• any discount from a coupon or an automatic offer;
• the total you will actually be charged, and the currency it will be charged in;
• any bonus credit, and the total credit that will land on your key.

The payment itself happens on the payment provider’s own page or widget. We never receive your card, bank or wallet details. Credit is added to your key only when the provider’s signed confirmation that the payment succeeded is received and verified, so there can be a short delay between paying and seeing the balance move.

Refunds are covered separately in the Refund Policy, which forms part of these terms.

Section 07. 07Promotions, codes and referrals# (permalink)

The operator may run coupons, automatic offers, bonus tiers, redeem codes and a referral programme. Where they do, the following applies.

• One promotion per order. A coupon you type and an automatic offer never stack; whichever is worth more to you is the one applied.
• Limits are enforced. Codes may carry a minimum order value, a maximum discount, a total usage cap, a per-key limit and a validity window. A code that fails any of these is simply not valid for that order.
• Redeem codes are once per key. A credit code can only be applied to a credit key, and a token code only to a token key.
• Referrals. A key can be attributed to at most one referrer, attribution happens the first time the referred key signs in, and a key cannot refer itself. The referrer earns a share of the referred key’s paid top-ups, which becomes claimable into their balance above a minimum. The percentage and the minimum are set by the operator and are shown on the referrals page.
• Bonus and reward credit is credit, not money. It is spendable on requests. It was never paid for, so it is not returnable as cash.

Promotions can be withdrawn or changed at any time, and abuse of them — creating keys to refer yourself, scripting redemptions, using codes not intended for you — may result in the credit being reversed and the key suspended.

Section 08. 08Your content and the model provider# (permalink)

You keep whatever rights you have in what you send and in what comes back. We claim no ownership of either and, as set out in the Privacy Policy, we do not store either: request and response bodies pass through the gateway and are not written to the database or to our logs.

To answer a request, its content is necessarily forwarded to a third-party model provider. That provider processes what you send under its own terms, which we do not control. Your API key is stripped before forwarding and is never disclosed to it.

Model output is generated text. It can be wrong, out of date, biased or fabricated, and identical or similar output may be produced for other users. It is not advice of any kind. Check anything you intend to rely on.

Section 09. 09Acceptable use# (permalink)

You agree not to use the service, or let anyone use your key, to:

• break any law that applies to you, or infringe anyone’s rights;
• generate material that sexually exploits children, incites violence, harasses or defames, or is designed to deceive people about who they are dealing with;
• build or operate malware, phishing, spam or credential-stuffing tooling;
• attack, probe or overload the gateway or the model provider behind it, evade the rate limit or the model allowlist, or attempt to reach the operator’s upstream account directly;
• attempt to obtain another customer’s key, session or data, or to derive a key from its stored hash;
• misrepresent generated output as human-authored where doing so would mislead someone to their detriment.

You are also bound by the acceptable-use rules of the underlying model provider, whether or not you have read them, since your requests are executed there. Where those rules are stricter than these, the stricter rule applies.

Section 10. 10Availability and change# (permalink)

The service is provided on an as-available basis. No uptime commitment, response-time target or support window is promised in these terms — if the operator has agreed one with you separately, that agreement governs, not this page.

• Models change. The catalogue, the rates, and which models a key may use can all change, including with little notice, because they follow what the upstream provider offers.
• Upstream failures pass through. When the provider is unavailable, rate limiting, or refusing the operator’s account, requests fail. Those failures are reported honestly and are not billed, but they cannot be prevented from this side.
• Maintenance happens. The service may be interrupted for deployment or maintenance.

Section 11. 11Suspension, expiry and termination# (permalink)

A key may be suspended, expired or deleted by the operator. In practice this means:

• Suspension — every request fails, and any signed-in session for the key is revoked. It is reversible: the same key works again if it is resumed.
• Expiry — the key stops working on its expiry date, even with credit remaining. The operator can extend it.
• Deletion — the key is gone permanently and cannot be restored.

We may suspend a key without notice where we reasonably believe it has been compromised, is being used in breach of section 09, is being used to abuse promotions, or where a payment made for it is reversed or charged back. Where the reason allows it, you will be told what happened and given a chance to put it right.

You may stop using the service at any time; simply stop sending requests and ask the operator to delete the key. What happens to any balance left on a key when it stops being used is covered by the Refund Policy.

Section 12. 12Warranties and liability# (permalink)

The service is provided “as is” and “as available”. To the fullest extent the law allows, we exclude all implied warranties, including those of merchantability, fitness for a particular purpose, accuracy and non-infringement. We do not warrant that the service will be uninterrupted or error-free, or that model output will be accurate, complete, current or suitable for any purpose.

To the fullest extent the law allows, we are not liable for indirect, incidental, special, consequential or punitive loss, or for lost profits, lost revenue, lost data, or loss arising from your reliance on model output — even if the possibility was known.

Where liability cannot lawfully be excluded, our total aggregate liability arising out of or relating to the service is limited to the amount you actually paid for credit in the three months before the event giving rise to the claim. Credit that was granted rather than paid for — bonuses, referral rewards, redeem codes — is not counted, because no money was received for it.

You agree to indemnify us against claims, losses and reasonable costs arising from your use of the service, from content you send through it, and from any breach of these terms by you or by anyone using your key.

Section 13. 13Governing law and disputes# (permalink)

These terms are governed by ⚠Not set: Governing law, and the courts of ⚠Not set: Jurisdiction have jurisdiction over any dispute arising out of them, without prejudice to any mandatory right you have to bring proceedings where you live.

Before starting proceedings, please raise the problem with us first — most disputes about a charge or a key are settled by looking at the record. Open a ticket at /dashboard/tickets or write to support@korlogic.com.

If any clause of these terms is found unenforceable, the rest continues to apply. A failure to enforce a clause is not a waiver of it. You may not transfer your rights under these terms without our consent; we may transfer ours as part of a transfer of the business, on notice.

Section 14. 14Changes to these terms# (permalink)

These terms may change as the service changes. The revision date at the top of this page is the operator’s record of when they were last substantively updated; where no date is shown, none has been recorded.

Continuing to send requests after a change means the current version applies to you. If a change is unacceptable, stop using the key and ask about any unspent balance — see the Refund Policy.

Section 15. 15Contact# (permalink)

The fastest route is a support ticket at /dashboard/tickets, because it is tied to your key and the operator can see the record behind your question. If you cannot sign in, use the contact page or write to support@korlogic.com.

Privacy questions go to privacy@korlogic.com. Postal notices go to the registered address in section 01. When you write about a key, quote its prefix — the visible first characters, for example kl_live_a1b2c3d4 — never the whole key.