Quorum Enterprise API

The Quorum Enterprise API gives your software direct access to Quorum's services.

Attest takes a claim and the evidence behind the claim and tells you whether the evidence supports it, contradicts it, or says nothing about it, pointing at the exact sentences it relied on.

Kerf takes a web address and gives you the page as Markdown, in the order a person reads it rather than the order of the markup. See Pages as Markdown.

Base URL: https://api.quorumtech.ch

Every request carries a bearer credential and every response is JSON. The API is available over plain HTTP and, for AI clients such as Claude and ChatGPT, as an MCP server on the same code path.

What Attest is for

You have a sentence a person or a model wrote, and the documents it was written from. Attest checks the sentence against those documents and returns one of five verdicts: SUPPORTED, PARTIALLY_SUPPORTED, INSUFFICIENT_EVIDENCE, CONTRADICTED or DISPUTED. Beside the verdict come the supporting and contradicting span ids, a span-cited explanation, an audit of that explanation, and a provenance block naming every version and hash that produced the answer.

Typical uses:

• Check every factual sentence of a generated draft before it reaches a reader.
• Review a board paper, a briefing or a report against the pack it was written from.
• Gate a retrieval pipeline so a sentence the retrieved documents do not establish is flagged rather than shipped.

The one thing to understand first

A verdict is relative to the evidence you supplied. SUPPORTED means "consistent with the documents you handed me", never "true in the world". Attest does not search for evidence and never rules on the world, only on what you sent. Models measure, deterministic code decides, and the decision is reproducible from the hashes in the provenance block.

Two ways to send evidence

• Inline, in the request: up to 50 evidence items and 200,000 characters. One model call, one credit. Best when you already hold the passages the claim came from.
• As a loaded batch: upload documents once (PDF, Word, PowerPoint, text or Markdown, up to 200 files), receive a batchId, then check as many claims as you like against it. Attest searches the batch itself, so this costs two credits a claim. Best for reviewing a document against a pack.

Batches and drafts live in memory only and expire after six hours. Nothing you send is written to disk or a database. See the Privacy page.

How you reach it

| Surface | Credential | Where | | --- | --- | --- | | Attest over HTTP | an API key, Authorization: Bearer <key> | https://api.quorumtech.ch/attest/v1/... | | Kerf over HTTP | an API key with the kerf scope | https://api.quorumtech.ch/kerf/v1/... | | Attest as an MCP server | Connect with Quorum, or an API key | https://api.quorumtech.ch/attest/mcp | | Documentation playground | your signed-in session, on these pages | the "Try it" panel on every endpoint page |

What you need

1. A Quorum account. Sign in at https://developer.quorumtech.ch. A developer without a company workspace gets a personal one on registration.
2. Credits. A new personal workspace claims 250 starting credits by linking a card on the Billing page, and nothing is charged. Any workspace can buy a credit pack or take a plan. One credit is one cent, and a price may be a fraction of one: a page fetched by Kerf costs a tenth of a credit.
3. An API key for code that cannot sign in, created by a workspace owner or admin on the API keys page, or an MCP connection for an AI client, which any member can make with their own account.

The Quickstart takes you from sign-in to your first verdict in a few minutes.

Versioning

The HTTP surface is under /v1. Fields are added, never removed or renamed, within a version. Every response's provenance.serviceVersion names the build that produced it, so a change in behaviour can always be tied to a version.