API Terms of Service

1. Scope

The Lenz API exposes two primitives: POST /extract (claim extraction) and POST /verify (multi-model verification). "You" refers to the holder of an API key and to any entity on whose behalf the key is used. By creating an API key or making an API request you accept these Terms.

2. API Keys

Your API key authenticates requests as you. You are responsible for keeping your key confidential — do not commit it to public source repositories, expose it in client-side code, or share it with third parties. You are responsible for all traffic and charges incurred through your key until you notify us (via contact or by revoking it in your API integration settings) that the key may be compromised. Once revoked, the key is invalidated immediately and we will not charge you for subsequent traffic on it.

Rotate keys when team members leave or when you suspect exposure. We may suspend a key without notice if we detect abuse, fraud, or traffic that materially impacts service stability for other users.

3. Rate Limits and Quotas

Quotas are enforced per API key:

• POST /extract — 1,000 calls per key per day, free on all tiers.
• POST /verify — quota varies by subscription tier. Pro includes 500 verifications and 1,000 follow-up questions per month. See subscription plans for current limits and Plus/Free tier quotas.

Limits are soft-enforced: bursts above the limit may be served or may return 429 Too Many Requests depending on aggregate load. We provide no SLA on burst capacity. If you need higher or guaranteed throughput, contact us about Enterprise terms.

4. Using Verdicts in Your Product

You may embed Lenz verdict text, scores, and citation lists in your own product. Two limits apply:

• You may not represent Lenz as having "certified", "approved", or "endorsed" a claim. Lenz returns evidence-based assessments, not authoritative truth.
• You may not resell raw API access (reselling a wrapper around /verify as a verification API of your own). You may resell products that embed verdicts as part of a broader service (research reports, compliance findings, document review).

5. Data We Process

Text submitted to /extract and /verify is processed by Lenz and by third-party large language model providers as described in our Privacy Policy.

Claims accepted by /verify may appear on the public corpus at /c/<slug>. If your use case requires that submitted claims remain private (for example, internal document review), set the request visibility parameter to private on submission — see the API documentation for the full request schema. Private claims are still stored, just not exposed on the public corpus.

Do not submit personal data, payment card data, health records, or other regulated data that you are not authorised to share with third-party LLM processors. You are the data controller for any text you submit; we are the processor.

6. Service Availability and Changes

The Lenz API is provided on a best-effort basis. We do not offer an uptime SLA on standard tiers. Outages, planned maintenance, and material API changes are reflected in the API documentation and, where applicable, communicated via email to the address on your account.

We may add new endpoints, parameters, response fields, or performance improvements at any time. We provide at least 30 days' notice before removing endpoints or making breaking changes to existing response shapes. Model versions used inside the verification pipeline may change without notice; the verdict shape remains stable.

7. Verdict Accuracy

Lenz returns evidence-based assessments produced by a multi-model pipeline. Verdicts may be wrong. They are intended as a research and verification aid, not as authoritative truth. You are responsible for any decisions or actions taken on the basis of a verdict, including how you present verdicts to your end users.

8. Indemnification

You agree to indemnify and hold harmless Lenz, its operators, and its officers from any claim, loss, liability, or expense (including reasonable legal fees) arising from (a) how you present, distribute, or rely on Lenz verdicts in your own product, (b) your breach of these Terms or the general Terms of Use, or (c) your violation of any applicable law in connection with your use of the API.

9. Limitation of Liability

To the maximum extent permitted by law, our aggregate liability to you for any claim arising out of or relating to the API is limited to the greater of (a) the fees you paid for the API in the twelve months preceding the event giving rise to the claim, or (b) €100. We are not liable for indirect, incidental, special, consequential, or exemplary damages.

10. Termination

We may suspend or terminate your API access immediately for breach of these Terms, the general Terms of Use, or for abuse, fraud, or activity that materially impacts service stability. For paying customers in good standing whose access we wish to terminate for reasons other than breach, we provide at least 30 days' written notice and a prorated refund of unused prepaid fees on the active billing period.

You may terminate at any time by revoking your keys and cancelling your subscription in API integration settings and subscription settings. We do not refund partial billing periods on customer-initiated cancellation.

11. Governing Terms

The general Terms of Use and Privacy Policy apply to API users where not overridden by these API Terms. Where there is a conflict, these API Terms control for API usage. Governing law, dispute resolution, and severability provisions of the general Terms apply.

For questions about these API Terms, contact us through our contact page.