Using the Quorum Enterprise API

The Enterprise API lets your own software and your AI tools use Quorum's services directly. Today that is Attest, which checks a claim against your documents and shows the sentences behind every verdict; Kerf, which turns PowerPoint decks into faithful Markdown, is coming. You manage everything from the API dashboard at developer.quorumtech.ch, which appears as "API" in the app switcher.

Two ways in

Connect with your Quorum account. Any member of your workspace can add Attest to Claude or another MCP client and choose "Connect with Quorum". You approve the connection once, it then acts as you with your workspace's limits, and it shows up under Connected clients on the dashboard where you or an admin can disconnect it at any time. This needs no key and no setup from us, only credits on your workspace, which the next section explains.

API keys. A key is a standing credential for software that cannot sign in, such as a server-side agent or a pipeline. Keys are created by a workspace owner or admin on the API keys page, shown once, and scoped to the services they may reach. Each key has its own limits and its own usage.

Getting API access

You do not need to ask us for anything. Create a developer account at developer.quorumtech.ch with no card and you get a personal workspace straight away. On the Billing page, link a card to claim 250 starting credits. It is a Stripe page that saves the card and charges nothing, and nothing is ever charged unless you buy a credit pack, switch auto top-up on or take a plan. Each person, and each card, can claim the starting credits once. In India, Pakistan, Bangladesh and Nepal a card cannot be checked for nothing, so the credits are claimed with a card check instead: $1, shown in your own currency, charged through Stripe and refunded as soon as it goes through. It buys nothing and no card is stored, and your bank may take a few days to show the refund. A card issued in India cannot be charged while you are away under the Reserve Bank of India's rules, so auto top-up and monthly plans are not offered for it and we email the workspace's owners when the balance runs low.

The moment the credits land, you can create keys on the Keys page and connect Claude or another MCP client with Connect with Quorum. Buying a credit pack or taking a plan switches the same things on for any workspace, including a company workspace.

A credit is one cent. Checking a claim costs one credit when the evidence is in the request and two when it is checked against your uploaded documents, and a whole draft review costs two for every claim it checks. What packs and plans cost, and how a draft review is charged, are in "Enterprise API credits and pricing"; how a review runs, and what its verdicts mean, are in "Reviewing a whole draft with Attest". Once your credits are spent, requests that check a claim get a 402 until you buy more; nothing is billed automatically. Connect with Quorum is gated the same way: without credits or a contract the connection is refused with a 402 that names the Billing page.

Enterprise clients on a contract have API access switched on by us instead, and the contract can also cover custom limits, invoicing and a data processing agreement. If that is you, ask Quincy in the corner of the dashboard or contact support.

Limits and usage

Every credential may make a number of requests a minute, check a number of claims a minute, and check a number of claims a day, shown on the Usage and limits page with what each credential has used right now. Over a limit the API answers with 429 and says when to retry. A workspace without a plan runs at pay-as-you-go limits; a plan raises them, and an admin can set a key's limits anywhere up to the plan's. The dashboard counts only what you asked for: the handshake an MCP client performs when it connects is not counted.

Privacy

Attest never stores the claims or documents you send. The dashboard shows counts and which routes were called, never the content.