The same work as the extract call, with the request held open until the page is done and the Markdown returned directly.

Server-sent events for one job: its state now, every change after it, and the finished page. Closes when the job does.

One frame of a job's state without its Markdown, for a progress bar that should not carry a page's text with every poll.

Poll a job that answered 202. Returns its state while it runs and the Markdown once it is done.

Give Kerf an address and get the page as Markdown, in the order a person reads it, as a job you can wait for or collect.

A server-sent event stream of a review's progress, ending when the review does. It never carries the result.

One progress frame for a review that is still running, without collecting it or settling its bill.

Poll a review that answered 202. Returns progress while it runs and the full result once it is done.

Check every claim in a draft against a loaded batch. Attest extracts the claims itself, splits compound sentences, and returns one result per claim in draft order.

Drop an uploaded draft from memory once its review is collected.

Upload the draft to review as a file, so the review runs against the exact bytes you hold and the returned hash proves it.

Drop a batch and every document in it from memory, once the work is done.

The batches currently held in memory, with their sizes, hashes and creation times.

Upload up to 200 PDF, Word, PowerPoint, text or Markdown files into a batch, parsed on the server, each with the hash that proves which bytes were checked.

Load up to 200 documents as text into a batch you can check claims and drafts against, when you hold the text rather than the files.

Check up to 100 claims in one call. Results come back in the same order, one slot per claim, so a failed check never shifts the verdicts after it.

Check a single claim against evidence sent in the request or against a loaded batch, and get a verdict with the spans it rests on.

How the Documentation tab works: the playground that sends real requests as you and charges your workspace, the code samples, search, Quincy, and the plain-text copies for AI tools.

Add Attest to Claude, ChatGPT or any MCP client, connect it with your Quorum account or an API key, and what the tools and the /attest command do.

What Kerf does with a web page, how to ask for one, what the two fetch paths mean for you, and what is kept.

The error shape, the full catalogue of error codes with what each means and what to do, and which status codes are safe to retry.

Requests per minute, claims per day and claims per minute per credential, the headers that report them, what a 429 carries, and how to retry.

One credit is one cent. What each call costs, how a request is reserved and settled, the headers that say what it cost, starting credits, packs, plans, auto top-up and the refusals you see when credits run out.

How Attest was measured, what each figure counts, the two caveats that go with them, and which number to build on.

What the API keeps and what it never does. Attest never persists files, evidence or claims, Kerf holds a fetched page only as long as its job, and the gateway records counts only.

Upload documents once as a batch, upload a draft, and let Attest find and check every claim in it, with the hashes that prove which bytes were reviewed.

What the explanation, audit, provenance and degraded fields of a result mean, how to use them for an audit trail, and when to switch the explanation off.

How to send evidence, how to name it, how span ids like ev_1:0 point back at your sentences, and the limits on a request.

The five verdicts Attest returns, what each means relative to your evidence, why PARTIALLY_SUPPORTED is the one to act on, and why INDETERMINATE is a 503 rather than a finding.

The developer landing page runs real checks on a demo token: the examples on the page, and a few sentences of your own, with no account, no key and nothing charged. What the demo allows and where it stops.

API keys for code, Connect with Quorum for MCP clients, and the playground for these pages: what each credential is, who can create it, and how it is checked.

From sign-in to your first verdict in five minutes, with the request in curl, JavaScript and Python and the response explained line by line.

What the Enterprise API is, what Attest does, how you reach it over HTTP and MCP, and what you need before your first request.

How an Attest draft review works: upload the documents and the draft, Attest finds the claims itself, progress moves while it runs, the 200-claim limit and the cursor that continues past it, what each verdict means, and why a contradiction always cites a sentence.

What Attest costs over the Enterprise API: one credit is one US cent, a claim costs one credit with its own evidence or two against a loaded batch, a draft review costs two per claim it checks. Starting credits, packs, auto top-up, plans, metered billing, refusals and how to read the statement.

The two ways to use Attest over the Enterprise API: connect an MCP client with your Quorum account, or create API keys for software that cannot sign in. Both switch on the moment your workspace has credits, either the 250 starting credits you claim by linking a card or a credit pack you buy; in India, Pakistan, Bangladesh and Nepal they are claimed with a card check instead: a dollar in your own currency, charged and refunded straight away, with no card stored. How credits are spent, how limits work, and what the dashboard shows.

Where Teams chat and channel files live, how they reach Quorum through your Microsoft 365 connection, and how to resync them.

A plain-language tour of the security around your documents: workspace isolation, encryption at rest, audited access for automated services, and offboarding guarantees.

How deletion works, why it is admin-only and permanent, how synced files behave when deleted, and what happens to your data when you leave.

Download single files or a selection at once, and understand why download links are short-lived.

How the search box on the Files page works, and how content indexing helps briefings find the right documents by meaning.

How visibility works inside a workspace and what workspace admins can do that members cannot.

Create folders, move files one at a time or in bulk, rename folders, and understand which folders sync manages for you.

How to add files by drag and drop or with the Upload buttons, the 100 MB per-file limit, and how uploads are indexed for briefings and search.

The 'Sync personal files' security setting lets workspace admins decide whether personal drives are included in Microsoft 365 sync or only shared site libraries.

Which files and folders Quorum imports from Microsoft 365, the 30 MB per-file limit, how often sync runs, and how deletions and renames are mirrored.

How a workspace admin connects OneDrive and SharePoint, what the Microsoft 365 admin approval step looks like, and what happens during the first scan.

What the spinner and the warning triangle next to a file mean, how long indexing takes, and which files legitimately produce no searchable text.

What to do when a connection is stuck on admin approval, shows a sync error, imports fewer files than expected, or files you deleted keep coming back.

Every message the Teams calendar connection can show, what it means, and who can fix it.

What to do when a scan fails, an episode fails, audio is missing, or a meeting will not accept changes.

The reasons a Quorum session ends, what happens across your other Quorum tabs and apps, and how to get back in quickly.

Why a Quorum app sometimes shows a page saying the service is unreachable, and what to do while it recovers on its own.

Why nothing loads or you get signed out when you are on holiday, abroad, travelling, working from another country, on hotel or airport wifi, or using a VPN, and exactly how to get back to work.

Create a listen link for a briefing episode, choose who can open it and for how long, and know what ends a link's life.

The visibility and permission rules for meetings, episodes, editing, and deletion.

The episode player, the synced transcript, playback speeds, and installing the dashboard as an app on your phone.

Why Quorum waits for team profiles before prompting the first podcast, and how to create it when the moment comes.

How briefings are counted against your monthly allowance, what each plan includes, and how overage is priced.

Create members-only or public listen links for a finished episode, choose how long they live, and understand what a link can and cannot do.

Use the Upcoming page to turn a Teams meeting into a briefing podcast with the details already filled in.

Link Microsoft 365 so upcoming Teams meetings arrive in Quorum ready to import, with a clear picture of what is read, kept, and never touched.

Admins control the show identity, delivery style, and content rules that every generated episode honours.

Tell Quorum what you work on so every briefing episode is tailored to your role, your domain, and your interests.

How the file review step works, what the Verify and Foundational badges mean, and how the time window chips change what the scan considers.

What happens between pressing Create podcast and hearing your episode, including the stages, the order, and how long it takes.

How to set up a meeting in the three-step wizard so every attendee gets a personalised briefing episode before they walk in.

What your browser needs for Quorum sign-in to work, why cookies matter, and how the shared session keeps you signed in across all Quorum apps.

The Quorum dashboards are designed to feel at home when installed on your device, with an app-like layout and a status bar that matches your chosen appearance.

How to search the Help Center, browse by topic, and use the support chat to get answers grounded in our help articles.

An overview of the Quorum plans, what a briefing is, and how monthly and yearly billing work.

Every Quorum app can switch between a light and a dark appearance. Your choice is remembered in your browser so the app looks the way you want on every visit.

Quorum is a family of connected apps. Learn what each app does and how to move between them with the app switcher in the top right corner.

What the marketing site sets, when it asks, and how to change your answer.

How subscriptions renew, how to cancel, when a payment is refundable, and how Quorum Partners differ.

Quorum commits to briefings arriving before the meeting, rather than to an uptime percentage, and explains why.

Storage, database and compute are in Europe. Three providers process text in the United States, and this explains which and why.

The three questions people ask most: whether we train on your content, whether we clone voices, and how much we read.

The four agreements that cover how Quorum is used and how it handles your data, and what each one is for.

Current prices for every Quorum plan, what each tier includes, and how to work out which plan costs least for your usage.

A tour of the My Account page: your profile, workspace details, app shortcuts, and security actions.

How Quorum's Team, Business, and Scale plans connect to your workspace, and how checkout activates a newly created workspace.

Why Quorum asks you to verify your email, how long the link lasts, and how to request a new one.

How to end your Quorum session on all devices and browsers at once, and when Quorum ends sessions for you.

How to change your Quorum password from My Account, and why your other devices are signed out when you do.

The difference between removing a member from your workspace and disabling their account, and what each does to their access.

What the Owner, Admin, Member, and Service bot roles can do, and the rules that protect the workspace owner.

How to send a member a fresh temporary password, and what changes for them when you do.

How workspace admins create accounts for team members, send sign-in details by email, and what invited users experience on first sign-in.

How single sign-on works across the Quorum apps, how the app switcher connects them, and why signing out anywhere signs you out everywhere.

How to sign in with your workspace, email, and password, what the workspace field means, and what to do when your account is temporarily locked.

How to create a Quorum account and workspace, how your workspace slug is chosen, and what happens right after you sign up.