Skip to main content
The web app at app.okrapdf.com is a visual surface over the same resources the CLI, API, and MCP server work with. Every noun in the sidebar maps to a resource you can also drive from a script or an agent — uploading a PDF in the browser and uploading it with okra upload create the same document.
Sign in with your okraPDF account. The same API key you use for the CLI and API is managed under Settings → API Keys.

Workspace

The left sidebar mirrors the resource nouns one-to-one:

Documents

Processed PDFs with markdown, page images, extracted tables, chat, and citations. The equivalent of okra documents and GET /v1/documents.

Files

Raw uploaded file assets that haven’t been turned into a processed document. Maps to okra files and /v1/files.

Jobs

Parse, render, and workflow jobs with live status and results. Maps to okra jobs and /v1/jobs.

Collections

Group documents and ask one question across all of them. Maps to okra collections and /v1/collections.

Tables

Materialized extraction tables built from your documents.

Workflows

Multi-step runs such as accessibility/compliance audits, with run history.

Settings

Settings is where you manage your account and the credentials the other platforms use:
  • API Keys — mint and revoke okra_* keys for the CLI and API.
  • Vendor Keys — store your own Anthropic / OpenAI / Google keys to run extraction on your own model.
  • Webhooks — subscribe to document and job events. See Webhooks.

One resource, every surface

The web app is never the only way to do something — it’s the human-friendly view of an agent-first platform.
ResourceWebCLIAPI
Upload a PDFdrag-and-dropokra upload <source>POST /v1/documents
Read a documentopen itokra read <docId>GET /v1/documents/{id}/full.md
Ask a questionchat panelokra chat "<q>" --doc <id>POST /v1/documents/{id}/chat/completions
Query a collectionCollections pageokra collections query <name> "<q>"POST /v1/collections/{id}/query

Open the app

Sign in and upload your first PDF.