Enterprise API Terms

1. What these terms add

Our Terms of Service describe the briefing service: calendars, documents, and audio episodes prepared for a meeting. The Enterprise API is a different product, bought a different way, and those terms do not describe it.

These terms cover the Enterprise API and Attest. Everything in the Terms of Service still applies, and where the two disagree about the Enterprise API, these terms win.

They are an agreement between Quorum Technologies GmbH, registered in Switzerland under number CHE-196.262.518 at Heumattstrasse 18, 8906 Bonstetten ("Quorum", "we", "us"), and the person or organisation whose workspace holds the credits ("you").

2. What the Enterprise API is

The Enterprise API is an HTTP interface at api.quorumtech.ch. Its first service is Attest, which takes a claim and the evidence you supply and returns a verdict on whether that evidence supports the claim, with the exact sentences it relied on.

You reach it either with an API key, or by connecting a client that speaks the Model Context Protocol to your Quorum account.

2.1 What a verdict is, and what it is not

This matters more than anything else in these terms, so it is stated plainly.

Attest never searches for evidence. It rules only on the documents you send it. A verdict of SUPPORTED means supported by what you supplied, and nothing more. Where what you supplied does not cover the claim, Attest returns INSUFFICIENT_EVIDENCE, and it cannot tell you whether no such evidence exists anywhere or your own retrieval simply missed it.

A verdict is a measurement of a claim against documents. It is not advice, it is not a finding of fact, and it is not a warranty that anything is true. You decide what to do with it. Clause 7 of the Terms of Service, on accuracy and what output is for, applies to every verdict.

3. Credits

The Enterprise API is paid for in credits, held by your workspace and spent as you use it.

One credit is one US cent. That does not change. Prices change by changing how many credits something costs, never by changing what a credit is worth.

Checking one claim against evidence you send in the request costs one credit. Checking one against a batch you loaded earlier costs two.

3.1 Where credits come from

• Starting credits. A new personal workspace receives 250 credits once. They are granted once per workspace and once per card, they are not replaced when spent, and a workspace that has had them cannot have them again.
• Credit packs. You may buy any amount from 5 US dollars to 10,000 US dollars at face value, in the currency described in clause 4.
• A plan's included credits. Each plan grants an allowance at the start of every billing period.

3.2 What expires and what does not

Credits you have bought do not expire. They stay in the workspace until they are spent.

A plan's included credits expire, at the end of the period they were granted for, and again when a subscription ends. What is left is not carried forward and is not refunded. Credits you bought separately are untouched by either event.

3.3 Credits are not money

Credits are prepaid access to the Enterprise API. They are not a deposit, they carry no interest, they cannot be transferred between workspaces, and they cannot be exchanged for cash. Clause 6 covers when we refund a payment.

4. Prices and the currency you pay in

Our prices are set in each market we sell into, and Stripe presents the one for where you are. The figure shown at checkout is the amount charged. It is a price we have set in that currency, not a conversion of a dollar price made at the moment you pay, so it does not move with exchange rates between one visit and the next.

The tariff itself is kept in US cents, because a credit is one US cent. Where your currency and ours differ, your bank may apply its own charges, which are between you and them.

We may change prices. A change to a plan's price takes effect at your next renewal, on the notice period in clause 9 of the Terms of Service. A change to what a claim costs in credits applies from the day it is published and does not affect credits you already hold.

5. The card check

Where your bank will not accept the zero-amount authorisation that linking a card normally uses, we check the card by charging a small amount and refunding it immediately. This applies today to cards issued in India, Pakistan, Bangladesh and Nepal.

The charge buys nothing. It is refunded as soon as it succeeds, and your 250 starting credits are granted with it. Your bank decides how quickly the refund appears, which is commonly five to seven days. No card is kept from a card check.

If the refund fails, tell us and we will return the money by another route. You are never expected to be out of pocket for a check.

6. Paying, and refunds

6.1 Credit packs

A pack is charged when you buy it and the credits are granted on payment.

If you have spent none of a pack, we refund it in full within 14 days of the payment. After that, or once any of it has been spent, the payment is not refundable, because the credits remain yours to use and do not expire.

If a payment for a pack is reversed, by you or by your bank, we take back the credits it granted. Where they have already been spent, the workspace's balance may go negative and the Enterprise API stops serving charged requests until it is settled.

6.2 Plans

Plans renew automatically, monthly, until cancelled. Cancelling stops the next renewal rather than ending the current period, and clause 3.2 governs what happens to the allowance.

Usage beyond a plan's included credits is charged at that plan's overage rate and invoiced. Each plan has a monthly cap on that overage. When you reach the cap the API refuses further charged requests with a 429 rather than continuing to bill you. An administrator may raise the cap.

6.3 Cards that cannot be charged while you are away

Where the rules for your card do not permit a charge without you present, we do not save the card, we do not offer automatic top-ups, and we do not offer plans. This applies today to cards issued in India, under the Reserve Bank of India's rules on recurring payments. Credit packs are unaffected, and we email the workspace's administrators when the balance runs low instead.

7. What we do with what you send

Attest keeps nothing. Claims, evidence and uploaded files are held in memory for as long as the request or the batch needs them and are never written to disk, to a database, or to any store that outlives the process. The verdict, the spans and the provenance live in the response and nowhere else.

The gateway records the route, the status, the latency and the number of claims of each call, so that we can bill you and keep the service running. It does not record the claims or the evidence. That request log is kept for 30 days.

This is narrower than the Privacy Policy allows for the briefing service, and it is deliberate. Where the two differ about the Enterprise API, this clause governs.

8. Using it fairly

Each plan carries limits on requests a minute, claims a minute and claims a day, published on the pricing page. They exist because the capacity behind Attest is shared, and they are enforced by the gateway rather than by invoice.

You must not send us content you have no right to send, use the API to build a competing verification service, or present a verdict as something Quorum has said about the world rather than a measurement against documents you chose. Clause 6 of the Terms of Service applies in full.

We may suspend an API key immediately where it is being used in a way that threatens the service for other customers, and we will tell you why.

9. Ending

You may stop using the Enterprise API at any time. Deleting your workspace forfeits any credits left in it, and clause 3.3 means they cannot be cashed out.

We may end these terms on 30 days' notice. If we do, we refund any credits you have bought and not spent, at what you paid for them.

10. Everything else

Governing law, liability, confidentiality, data protection and the rest are as set out in the Terms of Service.