Terms of service

In force from 2026-10-13.

1. Parties and acceptance

These terms are a contract between you and THINGS & STUFF, LLC, a Delaware limited liability company, 390 NE 191st St, STE 31817, Miami, FL 33179, United States ("Zabio", "we", "us"). "You" means the person or company that creates an account or uses the service. If you use Zabio for a company, you confirm that you can bind that company, and "you" means the company.

You accept these terms when you create an account, add credits, or send a request to the API. If you do not agree, do not use the service.

The Privacy Policy explains how we handle personal data. The Data Processing Agreement applies when you send us personal data of your own users as a controller. Both are part of these terms.

2. The service

Zabio is an AI router. You send requests in the OpenAI API format to our endpoints, and we forward them to a model at one of the vendors listed in the Privacy Policy and return the answer. We also offer stored conversations, prompt caching, a web app, a command line tool and usage reporting.

Model choice. When you name a model, we send the request to that model. If that model is unavailable or unhealthy, your key's fallback setting decides whether we try another model of the same vendor, any model of the same tier, or fail. When you request auto or auto/<tier>, a classifier chooses a tier and we choose the model within it based on cost, recent health, latency and residency. Every response tells you which model and vendor served it. We do not guarantee that any particular model or vendor will be available or will be chosen for a given request.

Third-party models. The models are built and run by the vendors, not by us. We do not control their output. A model may produce content that is wrong, incomplete, biased or unsuitable. You are responsible for reviewing output before you rely on it or pass it to others, and for the safeguards your use needs, especially for medical, legal, financial or other high-stakes decisions. Content a vendor refuses to produce is returned to you as a normal response with a content filter finish reason.

Availability. We work to keep the service available, but at this stage we do not promise any uptime level or response time. We may need to pause parts of the service for maintenance. Where practical we tell you in advance.

Beta. The service is in an early release phase. Features may change or be removed, limits may change, and errors are more likely than in a mature service. You use it with that understanding.

3. Accounts and organizations

You need an account with a verified email address. Keep your password and sign in methods secure. Tell us at once at legal@zabio.ai if you suspect that someone else has access to your account.

Everything in Zabio belongs to an organization: credits, API keys, members, projects, stored conversations and usage. The person who creates an organization is its owner. Owners can invite members, set roles (admin or member), set quotas, and transfer ownership.

Owner responsibility. The organization's owner is responsible for everything done in the organization: by its members, by anyone holding its API keys, and by any software that uses them. That includes all charges to the organization's balance.

API keys. A key is shown once when created. Keep keys secret. Do not put them in client-side code, public repositories or shared documents. If a key may have leaked, revoke it immediately; revocation takes effect at once. You are responsible for the use of a key until it is revoked. You can limit what a key can do with scopes, allowed models, rate limits, spend limits and an expiration; an expired key is refused.

Your own vendor keys. You may add your own Anthropic, OpenAI or Google API key. You confirm that you are allowed to use it with a router under that vendor's terms. Calls served with your key are billed to you by the vendor, not by us. If the vendor rejects your key, we stop using it and never fall back to our own key for that vendor.

4. Acceptable use

You may not use Zabio to:

• do anything illegal, or to create, store or send content that is illegal where you or your users are;
• break the usage policies of the model vendors. You must comply with the Anthropic Usage Policy, the OpenAI Usage Policies and the Google Generative AI Prohibited Use Policy, as each applies to the requests you send. A vendor's refusal or a complaint from a vendor about your traffic may lead us to suspend you;
• try to break the isolation between organizations, access another customer's data, probe or attack our systems, bypass rate limits or spend controls, or use the image URL feature to reach private networks;
• resell or offer the service to third parties as your own routing product without our written agreement. Building your own product on top of Zabio, where your users do not hold our API keys, is allowed;
• send traffic that harms the service or other customers, or that is intended to harvest or reverse engineer vendor models beyond what the vendor allows;
• use the service if you are under 18.

Limits. Each API key has a request per minute and a token per minute limit (600 requests and 200,000 tokens per minute by default, adjustable per key), and each client address has a request limit. Requests over a limit receive a 429 response with a Retry-After header. Request bodies are limited to 32 MB. We may change these limits with notice where practical.

5. Your content

Ownership. As between you and us, you own the content you send (inputs) and the content the models return to you (outputs). We claim no rights in either. Whether an output can be protected by intellectual property law, and whether it infringes someone else's rights, is beyond our control; you are responsible for how you use outputs.

Our use. We process your content only to provide the service: to route it to the vendor, to return the answer, to keep the conversations you ask us to keep, and to operate security and abuse controls. We never use your content to train or improve models, ours or anyone else's, and we do not allow vendors to train on it on our behalf.

Storage is opt-in. Chat completion and embedding calls store nothing beyond metadata by default. Bodies are stored only when you switch body logging on for a key, or when you use stored conversations. In both cases the content is encrypted and kept for the retention period your organization sets, from 1 to 365 days. You can delete stored content at any time through the API or the web app. Details are in the Privacy Policy and the Data Processing Agreement.

Metadata. We keep metadata about every call (time, models, tokens, cost, routing decision, outcome) to bill you, show you usage, and run the service. Metadata never contains your prompts or completions.

Your users. If your product exposes Zabio to your own users, you are responsible for giving them any notices and obtaining any consents the law requires, and for their compliance with section 4.

6. Fees and payment

Prepaid credits. Zabio is prepaid. You add credits in US dollars and every call is debited from your organization's balance. There are no subscriptions. A top-up pays only the fees on our pricing page, if any, shown before you pay and taken off the credit.

What a call costs. Every call is billed at the vendor's list price for the model that served it, plus the fees on our pricing page: a service fee on the vendor price of every call, and a fixed fee once per auto request for automatic model choice. We take no share of what routing saves you. Every response shows the vendor cost, each fee, the baseline and the saving. The baseline is what the same call would have cost on your key's baseline model, as our documentation describes; it shows the saving and never changes what you pay.

Your own keys. Calls served with your own vendor keys pay no service fee; their auto requests pay the fixed fee for automatic model choice. The vendor bills you directly.

Prices. Vendor list prices per model are published at GET /v1/models and in our documentation. They change when vendors change them or when we update the catalog. Your pricing plan (the fees on our pricing page and the minimum top-up) is versioned and shown on our pricing page and the Billing page. A change that raises a fee is announced at least 30 days before it takes effect, by email to every organization owner; a change that only lowers fees may take effect at once. A price or plan change applies to calls and top-ups made after the change and never rewrites past ones.

Adding credits. Credits are bought through Stripe, in the Billing page or on Stripe's payment page. The minimum top-up is on our pricing page and the maximum is 5,000.00 USD per payment. Credits are added when Stripe confirms the payment. To protect against card fraud, a new organization may add a limited amount per payment (today 50.00 USD) until two of its payments have cleared or it is 30 days old; the form states the limit while it applies. Your first top-up asks for billing details (a name, an address and, if you wish, a tax identifier), which we keep with Stripe and print on your receipts and invoices; you may edit them in Billing settings.

Saved cards. When you add credits you may choose to save the card. Stripe stores it; we keep only the brand, the last four digits and the expiry. By saving a card you authorize us to charge it later for the top-ups you request in one click from the Billing page and, if you turn automatic recharge on, for the automatic top-ups described below, including charges made while you are not present. You can remove a saved card at any time from the Billing page, which ends this authorization for future charges. Your bank may ask you to confirm a payment; a payment that is not confirmed is not charged.

Automatic recharge. Automatic recharge is off unless an owner or admin turns it on, which is possible only after a first successful top-up. When it is on, you set the balance below which we recharge, the amount we add each time (at least the minimum top-up) and a monthly cap (200.00 USD unless you change it). We charge your default saved card without further confirmation when your balance falls below the threshold, never more than once for the same drop and never beyond the monthly cap, and we email a receipt for each recharge. If a charge needs your bank's confirmation we email you a link to complete it; if a charge fails we retry once, then pause automatic recharge and email you; reaching the monthly cap pauses it until the next month. You can change the settings or turn automatic recharge off at any time; a change applies to the next recharge.

The Free plan. A new organization starts on the Free plan: no credit and no charge, with usage limits in place of a balance. The limits are published on the Billing page of our documentation and may change with notice where practical; today they are 100 successful requests a day, 20 a minute, 16,000 input and 2,000 output tokens per request, one member and two API keys, on the models of the free model list, which we may change at any time. Free also has a daily fair-use limit on what an organization's calls cost us; we do not publish its amount, and when it is reached the API says so and resumes the next day (UTC). Free is one organization per person: the first organization a verified person creates has the Free allowance; a later one needs a top-up before its first call. Free has no service level: we may change, limit or pause Free usage, including by account where we see abuse, with no compensation. Any top-up removes every Free limit and the account pays as it goes under this section. Trial credit granted before the Free plan existed is spent like any other credit and has no cash value. Any credit in your organization's balance, whatever its source (a top-up, promotional, referral or match credit, or credit we add), lifts the Free limits while it lasts.

Promotional credit. Zabio runs two launch offers, the match and referrals. Both apply to organizations in good standing, and Zabio may withhold or remove credit earned through abuse: self-referral, shared payment cards, fake or duplicate accounts.

• The match: one per account, in the account's first organization. If that organization is billed at least 250.00 USD in the 30 days after the account is created, every top-up to it after those 30 days is matched dollar for dollar, up to a total of 250.00 USD of match credit. Other organizations of the account and invited users have no match; a transferred organization keeps its match.
• A top-up that earns a match cannot be refunded. If a matched top-up is disputed or reversed, Zabio removes the match credit it earned.
• Referrals: the referrer receives 25.00 USD of credit when an organization created through their link by a new user has added 100.00 USD in top-ups, once those top-ups are 30 days old and undisputed.
• Promotional credit pays for any call, does not expire, has no cash value, and cannot be transferred or withdrawn.
• Zabio may end these offers for new qualifications and new referrals at any time. Credit already granted keeps its terms.

Refunds. Credits are not refundable, except where the law requires it or where we decide to refund at our discretion. Trial credit and promotional credit are never refunded, Free usage is not a credit and has nothing to refund, and a top-up that earned match credit is not refundable. If you believe you were charged in error, write to legal@zabio.ai with the Stripe session identifier or the ledger reference. Refunds are made through Stripe and reduce your balance accordingly.

Moving credit between your organizations. The owner of two organizations can move paid credit from one to the other from the Billing page, within the limits shown there: how long ago the credit was paid, how often, and never while either organization is suspended or has a disputed payment. Trial, promotional, referral and match credit cannot be moved. A transfer is recorded in both organizations' billing history and is neither a payment nor a refund.

Zero balance. When your balance is at or below zero, your organization runs on the Free plan's limits until your next top-up: every response says so, the dashboard shows it, and we email the owners and admins. Your keys and members are unchanged; only the Free limits and the free model list apply. You may instead set the organization to stop at zero, in which case the API refuses new calls with a 402 response before any vendor work is done; a person's second organization, which has no Free allowance, is refused the same way. A call already admitted may take the balance slightly negative; you owe that amount and it is deducted from your next top-up. Calls that your own vendor keys can serve entirely keep working in every case. None of this is a breach: no penalty applies, and everything resumes as soon as you add credits.

Spend controls. You can set a spend limit per key, which resets every day, week or month or covers the key's whole life, and a monthly quota per member. When a limit or quota is reached, calls on the affected keys return a 429 response until it resets. Limits are a tool for you; you remain responsible for all usage within them.

Taxes. Prices are in US dollars and do not include taxes. You are responsible for any sales, value added or similar taxes that apply to your purchases, except taxes on our income. Where we are required to collect tax we add it at checkout.

Disputes. Tell us about a billing dispute within 60 days of the charge, before disputing it with your bank: a refund through Stripe reduces your balance and nothing else changes. If a card payment is disputed with the bank (a chargeback), we suspend the organization at once, its API keys stop working and we review the dispute before reactivating it; promotional credit earned by the disputed payment is removed. The ledger and call records are our record of usage.

7. Changes to the service and the model catalog

Models come and go. Vendors release new models, retire old ones and change prices. We may add, remove or reprice models, change which models auto may choose, and change the tier of a model. Where practical we give notice through the web app, our documentation or email before a model you have used recently is removed. A request that names a removed model receives a 404 response; your fallback setting may route it to another model where you allowed that.

We may also change or remove features of the service. For changes that reduce what you can do, we give reasonable notice where practical. If you do not agree with a change, you may stop using the service and close your account.

8. Suspension and termination

By you. You may stop using the service at any time. An owner may delete the organization from Settings in the web app, and you may delete your personal account from Settings once you no longer own an organization that has other members or a balance. Unused credits are handled under section 6.

Zero balance. Running out of credits is not a termination. Your account and data stay as they are, your organization runs on the Free plan's limits (or stops, by your setting), and everything resumes when you add credits.

By us. We may suspend an organization, with or without notice depending on urgency, if we reasonably believe that it is breaking section 4, that its keys are being used for fraud or abuse, that its traffic threatens the service or other customers, or that a vendor requires it. A suspended organization receives a 403 response on every call. We will tell you why and, where the problem can be fixed, how to fix it. We may terminate an account for a serious or repeated breach, or if we discontinue the service, in which case we give at least 30 days notice and refund unused paid credits.

What happens to your data. When an organization is deleted, its API keys stop working at once, its stored conversations and logged bodies are deleted at once, and the encryption key that protected them is destroyed 30 days later, making any remaining copy unreadable. Everything else about the organization is deleted within 30 days, except billing records, which we keep for the period accounting law requires, and, for an organization suspended for fraud or abuse, the evidence described in the Privacy Policy. Sections 5, 9, 10, 11 and 13 survive termination.

9. Disclaimer of warranties

The service is provided "as is" and "as available". To the extent the law allows, we make no warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, accuracy of outputs, or non-infringement. We do not warrant that the service will be uninterrupted, error free, or that any model will remain available. Some jurisdictions do not allow some of these exclusions; in that case they apply to the extent permitted.

10. Limitation of liability

To the extent the law allows, neither party is liable to the other for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill, arising from these terms or the service, even if advised of the possibility.

To the extent the law allows, our total liability for all claims arising from these terms or the service in any 12 month period is limited to the greater of (a) the fees you paid us in the 12 months before the event giving rise to the claim and (b) 100 US dollars.

These limits do not apply to liability that cannot be limited by law, such as liability for wilful misconduct, gross negligence, or death or personal injury caused by negligence.

11. Indemnity

You will defend and indemnify us against third-party claims, and the resulting damages, costs and reasonable legal fees, that arise from your content, your use of the service in breach of section 4, or your products and services that use Zabio. We will notify you promptly of any such claim and let you control the defence, and we will not settle a claim in your name without your consent.

12. Third-party services

The service depends on third parties: the model vendors, Stripe for payments, and our hosting and network providers. Their terms apply to their part of the service. In particular, the content of your requests is processed by the vendor that serves them under that vendor's API terms. We are not responsible for the availability, output or policies of third-party services, but we choose them with care and we list our sub-processors in the Privacy Policy.

Links to third-party sites or documentation are provided for convenience and do not mean that we endorse them.

13. Governing law

These terms are governed by the laws of the State of Florida, United States, without regard to its conflict of laws rules, and the state and federal courts located in Miami-Dade County, Florida, have exclusive jurisdiction, without prejudice to any mandatory consumer protection rules that apply where you live.

14. Changes to these terms

We may update these terms. When we do, we change the date at the top. For changes that matter to you we give at least 30 days notice by email or in the web app before they take effect, except where a change is needed to comply with the law, in which case it may take effect sooner. If you continue to use the service after a change takes effect, you accept it. If you do not agree, stop using the service before that date.

15. Contact

THINGS & STUFF, LLC 390 NE 191st St, STE 31817, Miami, FL 33179, United States legal@zabio.ai