Use it for lawful things. We route your requests to the best place we can find and tell you honestly when we cannot. You own what you send and what comes back. One flat fee covers the whole service. You can leave whenever you like and take everything with you.
Version 1.3In effect September 12, 2026Operator Scaled Minds
How to read this
Drafted by the engineering team so that every factual statement traces to running code. Not reviewed by a qualified data-protection lawyer. Last checked September 13, 2026.
Where we cannot yet make a commitment, the document says so, dates it, and names what would close it. We would rather you found the gap here than found it yourself.
What would change that: A review is commissioned when the first controller who is not us signs the processing agreement, or at the first paid business customer — whichever comes first. It is deferred rather than skipped: today there is no customer to make these statements to.
What changed in this version: Prices are now read from the running service instead of typed into the contract, so the terms and the checkout can never disagree. Section 6 replaces a blanket no-remote-access claim with the exact commands a machine can accept and how to stop them. Section 11 states cancellation and closure as two separate effects, because they are.
A printed copy carries this version and its date, and leaves the
navigation behind.
1. Who this is between
These terms are between you — or the organisation you are acting for — and Host.Rodeo, operated by Scaled Minds. Using the service means accepting them. If you are accepting for a company, you are confirming you are allowed to. Scaled Minds' registered legal form and address are not published on this shelf yet; ask at [email protected] if you need the contracting entity confirmed in writing, and we would rather name that gap than imply a corporate form we have not verified.
2. What the service is
You point an app at one address. We decide where each request should go — free services, machines you own, or a paid service as a backstop — and return the answer with a signed receipt naming what handled it and what it cost. You can connect your own machines and your own provider accounts.
You never choose a model and you are never asked to. Choosing is the work this service exists to do, and a request that names a model is still served: we read what the request actually needs and route it.
3. Your account
Give us a real email address and keep your password to yourself.
Your API keys are bearer keys: anyone holding one can spend on your behalf. Treat them like cash, and revoke one from your account page the moment it leaks.
You are responsible for what happens under your account.
You must be 16 or older.
4. What you may not do
Anything unlawful, or anything that infringes someone else's rights.
Deliberately abuse the free services we connect to on your behalf — hammering them, or working around their limits. Their terms apply to that traffic, and abusing them costs every other person here.
Try to break, overload, or find your way into parts of the service that are not yours.
Resell raw access to the free lane as though it were your own capacity.
Route someone else's consumer subscription session through us, or ask us to help you do it. We win by being a good tenant of the services we use, out loud.
We may suspend an account that does these things. Where it is safe and sensible we will tell you first and give you a chance to fix it.
5. Your content, and ours
You keep everything you send and everything that comes back. We claim no ownership and no licence beyond what is needed to route your request and return the answer, and we do not train on it. The privacy notice says exactly what we keep and for how long; the sub-processor list says who else is involved.
You are responsible for having the right to send what you send, and for what you do with what comes back. AI output can be wrong, and it can be confidently wrong. Clint is an AI and says so; check anything that matters before it matters.
6. Your own accounts and machines
If you bring your own provider keys, that provider's terms govern that traffic and their charges are between you and them.
If you connect your own machine it stays yours, and here is exactly what that means rather than a blanket claim. We hold no remote shell and no inbound route: your machine dials out to us and nothing can dial in. Over that outbound channel it accepts a small, fixed set of signed instructions — take a piece of work, report what hardware and models it has, report that it is healthy, load or stop a model it already holds, and stop accepting work. It cannot be made to run arbitrary code, read your files, or install anything you did not install.
You can pause it, stop it or remove it from the machine itself at any time, and that is always your action rather than something we do to it. If it is switched off or unreachable we route around it; nothing waits on it.
7. Money
We could not read the current price as this page loaded, and we will not
print one from memory into a contract. The pricing page reads the same
running service, and a person will tell you if neither will load.
The trial needs no card. We ask for one only when you decide to carry on, and never before.
Free services and machines you own never add anything to that bill — but they reach you through Host.Rodeo, so if your access ends they stop answering through us as well. We tell you before that happens, not after.
If you use a paid service through us, you set the ceiling and we stop at it. Set no ceiling and we never spend anything on your behalf. A paid account you brought yourself is billed by that provider and never counts against this.
We will never invoice you for a number we cannot show you the arithmetic for.
Accounts opened before a price change stay exactly as they were until you explicitly accept the new one. Nobody is moved onto a charge without saying yes.
The amounts above are read from the running service when this page loads. They are the same numbers the checkout will ask you for, because there is only one place they exist.
8. What we promise, and what we do not
We try hard to always have an answer for you and we route around failures automatically. But we depend on other people's services and nothing is up all the time. We do not promise uptime. When something is down we say so plainly on the status page rather than pretending otherwise.
The service is provided as-is. To the extent the law allows we exclude implied warranties. Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot be limited by law.
9. Limits on liability
Neither side is liable for indirect or consequential loss, or for lost profits, revenue or data. Our total liability in any 12-month period is limited to the greater of the amount you paid us in that period, or 100 US dollars. If something goes wrong that limit is genuinely small — weigh that before putting critical work through here without your own fallback.
10. Businesses and data protection
If you send personal data through the service on behalf of your own users, you are the controller and we are the processor. The processing agreement covers that, including sub-processors, international transfers, breach notification and audits.
Two different things, and we keep them apart on purpose because a customer who does one and expects both ends up paying for a service they cannot reach.
Stopping the plan ends future charges. Do it from your account page. You keep everything for the rest of the period you have already paid for, and nothing is deleted.
Closing the account removes the account itself and revokes every key immediately. There is no notice period and no exit fee.
If you want both, stop the plan first and then close the account, and the page will say so as you go. If you have already closed an account and are unsure whether a charge is still running, write to us and we will check and stop it — you will not be charged for a service you cannot reach.
We may end an account for a serious or repeated breach of section 4, or with 30 days' notice for any other reason.
There is no lock-in by design: the API is the same shape as the one most AI apps already speak, so pointing your app somewhere else is a one-line change. That is the right way to earn the business.
12. Changes to these terms
We post any new version here with a new version number and date, and the previous version stays listed. We email account holders at least 30 days before a change that materially reduces your rights. Carrying on after that means you accept it; if you do not, close the account.
13. The boring end
If a clause is unenforceable, the rest still stands. Not enforcing something once does not waive it. You cannot transfer these terms without our consent; we can transfer them to a successor of the business. These terms and the ones they link to are the whole agreement. English law applies and the courts of England and Wales have jurisdiction — unless the law where you live gives you the right to your own courts, in which case you keep it.
Earlier versions
Every version this document has had. The one above is what you are reading now.
Version 1.3took effect September 12, 2026— current
Version 1.2took effect August 23, 2026
We do not publish the superseded text, because a stack of old contracts on
a public page is a way to be read out of context. The version you accepted stays retrievable: ask us naming the version and we will send you that exact text.
Questions about any of this reach a real person at the contact page, with or without an account — [email protected] for
anything about your own data, [email protected] for a security report. We answer within
10 working days.