Skip to content
OctoDoc

Agents and the CLI

Review the file from your terminal.

These account-free source-checkout tools inspect files you already hold. They do not create, prepare, send, or sign a file.

Local tools

Three local tools, one source checkout.

OctoDoc publishes no installer and no public source repository. If you already have an authorised source checkout, these three commands operate on files you provide.

  1. Review

    Inspect exact PDF bytes without an account, network request, or model call.

  2. Summarize

    Request a cited model summary after choosing the party whose perspective matters.

  3. Verify

    Compare a sealed PDF with an independently obtained digest, or replay a local ledger bundle.

Review locally

bun run octodoc <file.pdf> review [--json]

The result records the exact digest, page geometry, fields, structural signature facts, fonts, and signability reasons.

Choose machine output

The default output is TOON. Add --json only when another program needs JSON.

Both formats describe the same local result. Structured output goes to stdout; progress and disclosures use stderr.

Model boundary

A model call stays explicit.

Summarization is separate from deterministic review. It sends bounded canonical document text through Vercel AI Gateway and labels every model-selected result.

Disclosed network command

bun run octodoc <file.pdf> summarize --party <role> [--json]

The command requires a supported party perspective. Its cited summary is model output and is not a substitute for reading the complete document or for the advice of an attorney.

Verification

Verify the evidence you already hold.

The local verifier checks evidence you already possess. It does not look up a hosted OctoDoc record.

Sealed PDF

bun run octodoc verify --sealed <file.pdf> --sha256 <hex>

Obtain the digest independently. The structural signature-field result is not a certificate, trust, revocation, or legal-validity verdict.

Ledger bundle

bun run octodoc verify --ledger <bundle.json>

The verifier checks the bounded bundle, hash chain, Merkle proof, and RFC 3161 evidence against the selected local trust anchors.

Authority

Local inspection is not signing authority.

Local inspection creates no OctoDoc account state and grants no signing authority. Machine identity alone never authorizes a send or signature.

See the browser signing flowRead the authority modelAsk a question

Need a document signed? Use the supported browser product. The local tools on this page never place or confirm a mark, choose a party, or execute a binding act. Read the security boundary.