Terms and Privacy

These terms cover your use of the Serviqo API gateway and this website. Using a Serviqo key means you accept them. If you do not, stop using the key and speak to whoever issued it.

What Serviqo is

Serviqo is an API gateway. It exposes one endpoint that speaks both the OpenAI and the Anthropic request formats, and a fixed set of model tiers you select by name. You point an editor or an agent at the endpoint, present your key, and requests are served.

Tiers are described by what they do — context window, output limit, speed, and how quickly they consume credit. The specific model serving a tier is our operational choice and may change without notice; the tier name is the stable identity and the thing your configuration should depend on. We do not publish which model sits behind a tier, and support will not confirm it.

Keys, resellers and payment

Keys are issued by resellers. Serviqo does not sell keys on this site. There is no checkout, no pricing page and no account to sign in to, because there is nothing here to buy.

Your contract of sale is with the reseller who issued your key. They set the price, the credit balance, any expiry and any renewal, and they are the merchant of record for that sale. Invoices, receipts, refunds, chargebacks and billing questions are theirs to answer, not ours. Serviqo operates the gateway and enforces whatever budget, rate limit and model access is attached to your key.

Credit is a measure of how much of a key's budget remains. It is consumed at the rate the selected tier actually costs to serve, so the same number of tokens spends more credit on a higher tier. Credit has no cash value from us and cannot be redeemed with us.

Looking after your key

The key is the whole credential. Anyone holding it can spend its balance and read its status, so treat it like a password: keep it out of source control, out of screenshots and out of shared config files. Do not embed it in a client-side application, where every visitor can read it.

We cannot recover a key you have lost — we do not hold a copy you could be shown. Ask your reseller to reissue. If a key leaks, tell your reseller straight away so it can be revoked; you are responsible for usage on your key until it is.

Acceptable use

You may not use Serviqo to:

• break the law, or produce material that is illegal where you or your users are;
• generate sexual content involving minors, or material that sexualises real people without consent;
• produce malware, exploits, phishing pages, or tooling whose purpose is to compromise other systems;
• run spam, fraud, or impersonation of a real person or organisation;
• harass, threaten or target an individual or a group;
• probe, overload or work around the gateway's limits — including sharing one key across a userbase to dodge a rate limit, or attempting to read or use a key that is not yours;
• resell, sublicense or rebrand access unless your reseller agreement says you may, and on the terms it says;
• defeat or evade the safety systems of the models serving a tier.

You are responsible for what you send and for what you do with what comes back, including any obligation to tell your own users that a model produced it. Upstream providers apply their own policies to traffic we forward, and they can refuse or block a request regardless of what we would have allowed.

Availability and changes

The service is provided on a best-effort basis. There is no uptime commitment unless one has been agreed with you separately and in writing. We may add, change, throttle or retire a tier, adjust limits, and take the gateway down for maintenance. Where a change would break working configurations we will give notice through this site if we reasonably can.

No warranty

Serviqo is provided “as is” and “as available”, without warranties of any kind, express or implied, to the fullest extent the law allows. That includes fitness for a particular purpose, merchantability and non-infringement.

Model output is generated text. It can be confidently wrong, and it can reproduce patterns from its training data. It is not legal, medical, financial or safety advice. Read code before you run it and review output before you ship it.

Liability

To the fullest extent permitted by law, Serviqo is not liable for indirect, incidental, special or consequential loss, nor for lost profits, lost revenue, lost data or the cost of substitute services, arising from your use of the service.

Where liability cannot be excluded, it is limited to the amount paid for the key in question in the three months before the claim. Note that this amount was paid to your reseller, not to us; a claim about the sale itself lies against them.

Nothing here excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud. [Draft: confirm the correct carve-outs for the governing jurisdiction.]

Suspension and termination

We may block a key immediately and without notice where we believe it is being used in breach of the acceptable use section, where its traffic threatens the stability of the service or our access to upstream providers, or where we are required to by law. We will normally tell the issuing reseller why.

A key blocked for abuse forfeits its remaining credit as far as we are concerned; whether the reseller refunds anything is between you and them. If you simply want to stop, stop using the key and ask your reseller to revoke it.

[Draft: governing law and venue to be completed, along with the legal name and registered address of the operating entity.]

This covers what this website and the gateway do with data. It is short because the service is built to need very little.

No accounts, no tracking

There is no sign-in, no account and no customer database. We do not know your name or your email address unless you have written to us. This site sets no cookies, runs no analytics, embeds no third-party scripts, and loads its fonts from its own server rather than from a font provider.

The web server keeps ordinary access logs — IP address, timestamp, requested path, user agent — which is what any web server does and what is needed to keep it running and to deal with attacks against it.

The key checker stores nothing

Paste a key into the key status page and this is exactly what happens: the key is sent to our server over TLS, our server makes one call to the gateway asking that key about itself, the answer is rendered, and the request ends. The key is not written to a database, not saved in a cookie, not put in a log line, and not kept in memory past the response.

That is possible because a key can read its own record without any privileged credential, and a key asking about a different key is simply told it does not exist. This site never holds the gateway's administrative credential. It is a design constraint, not a policy we could quietly relax.

What the gateway records

For each API request the gateway records metadata so that spend can be metered and abuse can be found:

• the time of the request and how long it took;
• which key made it, and which tier was selected;
• input and output token counts, and the cost computed from them;
• the response status, and the error if there was one.

This is billing and operations data. It is what tells you how much credit you have left, and it is what we look at when a key is being abused. It is kept for as long as the key exists and for a period afterwards for reconciliation. [Draft: state the exact retention window here once it is fixed on the gateway.]

Who else sees your requests

To serve a request we forward it to an upstream model provider. That provider receives the content you sent, returns the response, and handles it under its own terms and retention policy. We do not publish which providers serve which tiers, for the reasons given in the terms above — but you should assume that anything you send to a hosted model leaves our infrastructure.

If your prompts contain personal data, confidential material or anything you are contractually obliged to keep in a particular jurisdiction, that is a decision to make before you send it, not after.

[Draft: a data protection regime such as the UK GDPR or the EU GDPR would require the sub-processors and transfer mechanisms to be named here. Complete this with legal advice.]

Your data and your rights

Because we hold no account, we generally cannot connect a key to a person. Your reseller can — they sold you the key and hold whatever details they collected. Requests to access, correct or delete personal data should start with them; where they need us to act on a key we will.

Traffic between you, this site and the gateway is encrypted in transit. Your key is a bearer credential: anyone who obtains it can use it, which is why the sections above are about not letting that happen.

Billing, refunds, renewals and anything about the sale: your reseller. They are the merchant of record and we cannot see the transaction.

Abuse reports, security issues and questions about this page: contact the operator of this deployment. [Draft: add the contact address and, if required, a postal address for the operating entity.]

Set-up documentation and the key status page answer most non-billing questions without needing to write to anyone.