← QuassLabs

QL API Terms of Service (Beta)

These terms cover the QL API at api.quasslabs.com, including its HTTP endpoints and its MCP gateway (the "API"). They add to our general Terms of Service. Where the two conflict, these terms control for the API. "We" means QuassLabs, Inc., a Utah corporation. "You" means the person or organization that gets an API key. If you sign up for an organization, you confirm you can bind it. You must be at least 18.

You accept these terms by ticking the agreement box when you sign up for a key. We record which version you accepted and when.

Read section 12 carefully. It requires individual arbitration and waives class actions, unless you opt out within 30 days.

1. Beta, as-is

The API is in beta. It is provided as-is and as-available, with no service level, uptime commitment, or warranty of any kind, including merchantability, fitness for a particular purpose, and non-infringement. We may change, rate-limit, or retire endpoints. We will try to give advance notice of breaking changes on docs.quasslabs.com.

2. Your key

Keys are issued through a one-time link we email you, and are tied to your account (the email address you signed up with). Keep your key secret. You are responsible for all use of your key, including use by anyone you gave it to or who got it because you exposed it. If you think your key is exposed, tell us and rotate it. We can revoke a key that has leaked or is being misused.

3. Credits and prices

4. Refunds and expiry

5. Acceptable use

Don't use the API to: break the law; attack, probe, or scan systems you don't own or have permission to test; send malware or content you have no right to send; get around rate limits, metering, or the free allowance (for example by creating multiple accounts or keys); resell or rebrand raw API access without our written OK; or interfere with the service or other customers. We may suspend or revoke keys that break this section, that put the service or others at risk, or that are linked to fraud or chargebacks. Where it's practical and safe, we will tell you why first.

6. Your content

You own what you send to the API (inputs) and what it returns to you (outputs), as between us. You give us permission to process inputs only to run your request, keep the service secure, prevent abuse, and meet legal duties. We do not use your inputs or outputs to train AI models. Some tools send inputs to service providers to do the work, including AWS Bedrock for AI model calls. We keep usage records (which endpoint, when, credits, status), not request content, for billing and abuse prevention, though some endpoints cache results for a short time. Section 3 of our Privacy Policy explains more. Don't send data you aren't allowed to share, and avoid sending sensitive personal data unless your request needs it.

7. AI output and high-risk use

Some tools use AI models, and many return analysis built from third-party data. Outputs can be wrong, incomplete, or out of date. They are analysis, not guarantees. A security tool returns risk signals; it does not certify that code or a system is safe. Land and location results come from public sources and are not a legal survey or title opinion. You are responsible for checking outputs before you rely on them. Don't use the API as the only basis for decisions about medical care, legal rights, safety-critical systems, or a person's credit, employment, housing, or insurance.

8. Limitation of liability

To the extent the law allows: neither of us is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, or data. Our total liability for all claims about the API is capped at the greater of US $100 or the amount you paid us for the API in the 6 months before the event that caused the claim. Some places don't allow these limits, so they may not fully apply to you.

9. Indemnity

You will defend and cover us against third-party claims arising from your inputs, your use of outputs, or your breach of section 5.

10. Ending this agreement

You can stop using the API and close your account at any time. We may suspend or end your access under section 5, or end the beta for everyone with 30 days' notice. Sections 4, 6 through 9, 12, and 13 survive.

11. Changes to these terms

We may update these terms. For material changes we will email you and post the update at least 30 days before it takes effect. If you keep using the API after that, the new terms apply. If you don't agree, close your account and section 4 applies. Changes to section 12 never apply to a dispute we already know about.

12. Disputes

13. General and contact

These terms, the general Terms of Service, and the Privacy Policy are the whole agreement about the API. If a part is unenforceable, the rest stands. You can't assign these terms without our consent; we may assign them with a sale of the business. Not enforcing a right is not a waiver of it. Contact and legal notices: contact@quasslabs.com, QuassLabs, Inc., 237 N 835 E, Lindon, Utah 84042.