Introducing RakeSign: Free, Unlimited Document Signing

The CloudRaker CLI

Install once. Call every capability from your shell, scripts, and CI pipelines.

View CLI docsGet API access
Setup

Install. Sign in. Run.

One binary, no runtime. You are processing documents from your shell in under a minute.

  1. 01

    Install the binary.

    One command: brew install cloudraker/tap/paperwork — or curl -fsSL https://paperwork.sh | sh anywhere Homebrew isn't. A single static binary for macOS and Linux, Apple Silicon and x86.

    HomebrewShell installer
  2. 02

    Sign in once.

    paperwork auth login opens the browser for a one-time device-code sign-in with your CloudRaker account. The token stores locally and refreshes itself. In CI, set PAPERWORK_TOKEN to an API key instead — a .env in the working directory is picked up automatically.

    Device flowAPI keys for CI
    See authentication docs
  3. 03

    Run the work.

    paperwork extract extract, paperwork parse parse, paperwork sign sign — every API endpoint is a subcommand. Parameters go in as flags or one --json payload; results come back as JSON your script pipes straight into jq.

    Every endpointJSON out
Built for scripts

The whole API, one command away.

The CLI is a thin, typed wrapper over the same /v1 API the SDKs use. Same runs, same audit trail, same output — just reachable from a shell.

JSON in, JSON out
Every command takes flags or a --json payload and prints structured JSON. Pipe it to jq, commit it, diff it.
Wait or poll
Small documents finish inline with --wait. Long jobs return a run id immediately; poll it or point a webhook at it.
Files upload once
paperwork files upload registers a document once; every later extract, fill, or redact reuses the id without re-parsing.
CI-ready auth
Interactive device-flow sign-in for humans, PAPERWORK_TOKEN for pipelines. The env var always wins when both are present.
Agent-ready
The paperwork skills teach coding agents to parse, extract, redact, fill, and sign through the CLI — without loading documents into context.
Get the agent skills
Every capability
Parse, extract, classify, split, merge, fill, compose, redact, redline, convert, sign — chained in any order your script needs.
Explore all capabilities
Why a CLI

Some paperwork belongs in a script, not an app.

The nightly batch that redacts yesterday's intake folder. The CI step that fills a compliance form on every release. The one-liner that pulls three fields out of a vendor PDF. None of that wants a browser tab or an SDK project — it wants a command.

Because the CLI fronts the same /v1 API as everything else, every run it starts shows up with the same audit trail, limits, and citations as runs from your app. Prototype in the shell, ship the same call in code.

Get started

brew install cloudraker/tap/paperwork

One command to install, one to sign in, and your free credits are ready to process real documents.

Install the CLIGet your API key