Introducing the Paperwork API: the whole platform, one surface

This week we shipped the parts. On Monday, rakedoc-nano, the open-weight vision model that reads the page. On Tuesday, RakeSign, free and unlimited e-signature, alongside our SOC 2 Type 2 report. On Wednesday, rakeaudio-asr, because a conversation is a document too.

Today is the whole. The Paperwork API is the surface those parts sit behind, and it is the thing we have been building for two years and never properly advertised. Every business runs on paperwork, and every piece of it boils down to the same repeatable actions. This API does all of them.

Six capabilities

Each one is one POST. Each one takes a file (a URL, or the id of a file you already uploaded) and returns a run. Runs share one status model, one expiry, one webhook contract. Learn one, you know all six.

Underneath them sit the primitives: parse turns a PDF, scan, office file, or recording into clean text and structure, classify finds document boundaries inside a packet, and split cuts along them without a model call. Pipelines run several capabilities over one file set in a single call, parsing each file once. And agents chain steps with built-in human sign-off, for the workflows where a person has to look before something goes out.

One call, with evidence

Here is the whole idea in one request. A document goes in with a JSON Schema. Data comes back shaped like the schema, and because citations is on, every field carries the page and the region it was read from.

curl -X POST https://api.cloudraker.com/v1/extract \
  -H "Authorization: Bearer $CLOUDRAKER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "file": { "url": "https://example.com/invoice.pdf", "name": "invoice.pdf" },
    "citations": true,
    "schema": {
      "type": "object",
      "properties": {
        "vendor": { "type": ["string", "null"] },
        "total":  { "type": ["number", "null"] }
      }
    }
  }'

{
  "output": {
    "value": { "vendor": "Northwind Fabrication Ltd", "total": 16796.70 },
    "citations": {
      "total": [
        { "fileId": "fil_…", "page": 0,
          "bbox": { "x": 0.71, "y": 0.62, "width": 0.11, "height": 0.02 },
          "text": "16,796.70", "confidence": 5 }
      ]
    }
  }
}

A recording is cited the same way, with a timecode in seconds instead of a page. A field the document does not contain comes back as null with a notFound citation. With citations on, every filled field is cited or declared absent. There is no third state.

The call holds until the run finishes, up to two minutes. If the document is slow, you get a 202 and a run id instead of a timeout. Point a webhook at the request and the finished run comes to you as a signed event: a JWT you verify against our public JWKS, with a body hash so a valid signature cannot be replayed onto a different payload.

No schema yet? Omit it, send a sentence of hints, and the platform infers one and reports it back on the run so you can save it. Prototype with hints, ship with a schema.

Same six verbs for humans, code, and agents

The API is one of three ways in, and they share everything.

• Code. npm install @cloudraker/api or pip install cloudraker. client.extract({ file, schema }) is the request above in one line.
• Terminal. The paperwork CLI runs every capability from a shell script or a cron job.
• Agents. The MCP server exposes the same verbs to Claude, or any agent, with the same citations coming back. We wrote about giving an agent a paperwork tool last month.

Everything runs on Canadian infrastructure, and the SOC 2 Type 2 report we published this week covers all of it.

Six examples you can run

Snippets lie. They skip the upload, the polling, the webhook server, the part where the result has to be checked. So we published six runnable apps instead, at github.com/CloudRaker/cloudraker-api-examples-typescript. Each one is a small Bun app with a web page, self-contained, MIT. Clone it, bun install, put your key in .env, bun app.ts.

Each example picks a different verb, a different kind of input, and a different way to prove the result. There is a short video for each.

Every one of them is small enough to read in a sitting and built to be stolen from.

Getting started

export CLOUDRAKER_API_KEY="sk_…"

git clone https://github.com/CloudRaker/cloudraker-api-examples-typescript
cd cloudraker-api-examples-typescript/medical-call-notes
bun install
echo "RAKERONE_API_KEY=$CLOUDRAKER_API_KEY" > .env
bun app.ts

Full reference for every capability, webhooks, pipelines, and agents: docs.cloudraker.com. Pricing: cloudraker.com/pricing. Grab an API key at signup.cloudraker.com.

Launch week: Day 1, rakedoc-nano · Day 2, RakeSign · SOC 2 Type 2 · Day 3, rakeaudio-asr · Day 4, the Paperwork API.