About these terms
These terms govern access to the Routehook website, dashboard and API. Together, the Platform. By creating an account, adding credits, or sending a request to the API, you agree to them.
If you are agreeing on behalf of a company or other organisation, you confirm that you are authorised to bind that organisation, and “you” means that organisation.
The contracting entity has not been settled.
- Legal entity name, registered address and company number
- Which entity contracts with customers in which regions
- Whether separate terms apply to business and individual accounts
Accounts
You need an account to use the API. You are responsible for the information on it being accurate, for the security of the credentials that reach it, and for everything done through it.
- Keep your contact details current. Billing and security notices go there.
- You are responsible for activity under your account, including activity by people you give access to.
- Tell us promptly if you believe an account or key has been compromised.
Account eligibility rules are not final.
- Minimum age and any restrictions on who may hold an account
- Whether team members, organisations or seats exist as account concepts
- Identity or business verification requirements, if any
Credits and billing
The Platform is prepaid. You add credits to your account, and a completed request deducts its own cost from that balance. There is no subscription and no monthly minimum.
- A request that fails deducts nothing.
- The cost of each call is reported on the response that caused it.
- Rates for each model are published on the pricing page and returned by the models endpoint.
Every commercial rule below is undecided. None is stated elsewhere on this site, and nothing should be inferred from the absence.
- Cancellations and chargeback handling (refunds are settled: see the Refund Policy)
- Whether credits expire, and on what schedule
- Taxes, VAT and who bears them
- Billing currency and how conversion is handled
- Notice given before a published rate changes
- Whether unused credits survive account closure
API keys and security
An API key is a credential. Anything sent with your key is treated as sent by you, so how you store and distribute keys matters more than any control we can apply after the fact.
- Keep keys server-side. Keys shipped to a browser or mobile client are treated as compromised.
- Use a separate key per project so revoking one does not take down another.
- Rotate keys when anyone with access to them leaves, and on any suspicion of exposure.
Incident handling is not defined.
- Where to report a compromised key, and how quickly we respond
- Whether we notify you of suspected compromise, and how
- What happens to usage billed against a compromised key
Acceptable use
Your use of the Platform is subject to the Acceptable Use Policy, which forms part of these terms. It covers what may not be generated, what may not be done to the Platform, and your responsibility for anyone you expose the API to.
Breaching that policy is a breach of these terms, and can lead to suspension or termination.
Your content
Inputs are the prompts, files and data you send to the API. Outputs are what a model returns for them. You are responsible for having the rights to the inputs you send, and for how you use what comes back.
Rights in inputs and outputs are the central commercial question here and have not been settled.
- Who owns or is licensed to use outputs, and on what terms
- The licence, if any, we need over inputs to route and serve a request
- How ownership interacts with each model provider's own position on outputs
- Whether identical outputs may be returned to other customers
Third-party model providers
Requests are served by models run by third parties. Their policies can apply to your use in addition to ours, and a provider can change, restrict or withdraw a model on their own timetable.
The pass-through position needs drafting.
- Which provider terms and policies are passed through to you
- How model changes, restrictions and withdrawals are notified
- What happens to work in progress when a provider withdraws a model
Availability and changes to the service
We intend the Platform to be dependable, and the documentation describes how it behaves when it is not. Status codes, retry guidance and rate limit headers. That is a description of behaviour, not a promise about uptime.
No availability commitment has been made anywhere on this site, and none is made here.
- Whether a service level commitment exists, and what it covers
- Maintenance windows and how they are announced
- Notice period before an endpoint or model is deprecated
- Remedies, if any, when a commitment is missed
Suspension and termination
You can stop using the Platform at any time. We may suspend or limit an account where use breaches these terms or the Acceptable Use Policy, where there is a credible security concern, or where we are required to.
The process around suspension is not defined.
- Notice given before suspension, and when it can be immediate
- How to appeal or restore an account
- What happens to a remaining credit balance
- How long account data is kept after closure. See the Privacy Policy
Disclaimers
Model output can be wrong, biased or unsuitable for a particular purpose, and the same input can produce different output on different calls. Check output before relying on it, particularly anywhere a mistake carries consequences.
The formal disclaimer has not been drafted.
- Warranty position and its wording, per jurisdiction
- Consumer rights that cannot be excluded and how they are preserved
- Any stated limits on suitability for regulated or high-risk uses
Limitation of liability
Deliberately left blank. Liability caps and exclusions are the kind of term that has to be written by a lawyer for a specific jurisdiction, and inventing one here would be worse than leaving the gap visible.
- Categories of loss excluded
- Any monetary cap, and how it is calculated
- Carve-outs that cannot be limited by law
Indemnity
Not drafted.
- Whether either party indemnifies the other, and for what
- Whether any IP indemnity is offered for model output
- Conduct-of-claims process
Changes to these terms
These terms will change as the Platform does. When they do, the updated version will be published on this page.
The change mechanism is not settled.
- Notice period before a material change takes effect
- How notice is given. Email, dashboard, or this page alone
- Whether continued use counts as acceptance, and what your options are if you disagree
Governing law and disputes
No jurisdiction is stated here, because none has been chosen. Naming one before that decision is made would be a claim about where you would have to bring a claim.
- Governing law
- Exclusive venue for disputes
- Whether arbitration or a class-action waiver applies
- Any informal resolution step required first
Contact
No legal contact route has been set up.
- Address for legal and contractual notices
- Email for terms questions
- Process for service of formal notice