space ocr icon

space ocr

space ocr turns documents into structured, searchable data with verification attached to each extracted value. It can be used in the browser, through a REST API, or as a Claude Code plugin/skill.

space ocr

Overview

space ocr is a document OCR product built to turn paper documents into searchable, structured data. It can read receipts, invoices, scans, PDFs, handwritten notes, faxed pages, and free-form layouts, then return results as fields, Markdown, or plain text with per-value or per-block evidence from the source image.

The product is presented as an app, an API, and a Claude Code plugin/skill. In the browser, users can upload documents into sheets, inspect each extracted cell against the original image, edit values inline, and query the resulting rows like a database with filters, sorting, projections, and pagination. Developers can automate the same workflow through API endpoints, batch jobs, and webhooks.

Features

Structured field extraction

Define fields once and upload documents into a consistent row-based schema. The product returns structured values that can be queried later as sheet rows or exported to CSV.

Verifiable outputs

Every extracted value carries the vertices it was read from, along with verification flags such as text_verified and needs_review. Users can jump from a cell back to the source pixels on the original image.

Server-side sheet queries

Query stacked rows on the server with filters such as where, sort, select, limit, and offset. The page also mentions a boxes flag to omit bounding-box payloads when they are not needed.

Multiple ways to use the same engine

Use the browser app, the REST API, or a Claude Code plugin/skill with the same extraction engine. The site also lists an MCP endpoint for agent workflows.

Document organization and export

Upload documents in batches, organize results in folders and Spaces, and search across folder names, memo bodies, and extracted cell values. CSV export is available with array-row expansion.

Developer-friendly workflow

The service supports async jobs, polling, HMAC-signed webhooks, OpenAPI 3.1, idempotency keys, per-key rate limiting, auto-rotation, and multi-script normalization for Japanese, Korean, Chinese, and English.

Use Cases

  • Invoice and receipt data entry

    Upload invoices or receipts, define the fields you want once, and get each document back as a row that can be sorted, filtered, and exported for accounting or review work.

  • Human review of extracted records

    Use the verification flags and source-image links to inspect questionable cells, correct them inline, and keep a record of where each value came from.

  • Archiving and search

    Process scans, handwritten notes, faxed pages, or mixed-layout documents into Markdown or plain text when the goal is searchable content rather than just field capture.

  • Developer automation

    Connect the API, batch upload, and webhook flow into an application or agent workflow that needs structured document ingestion without setting up a separate database.

  • Agent-assisted document workflows

    Run document extraction inside Claude Code or an MCP-compatible client when you want an assistant to file, query, and retrieve document data in place.

Pros and Cons

Pros

  • Turns document OCR output into structured, queryable rows instead of plain text only.
  • Keeps bounding-box evidence attached to extracted values, making it easier to verify results against the original image.
  • Supports multiple output formats: structured fields, layout-preserving Markdown, and reading-order text.
  • Can be used in the browser, through a REST API, or as a Claude Code plugin/skill.
  • Includes server-side querying, folders, CSV export, async jobs, and webhooks for automation.

Cons

  • The product page does not provide a full documentation set in the supplied sources, so some workflow details are only described at a high level.
  • The public material emphasizes verification and structured extraction, but it gives only limited information about edge cases, supported file limits, or failure handling beyond review flags and no-charge failures.

FAQ

What kinds of documents can it read?

Space OCR can read receipts, invoices, scans, PDFs, faxed pages, handwritten notes, and other free-form documents. The homepage also shows line-item and table extraction as part of the structured-field workflow.

How is this different from regular OCR?

Regular OCR usually returns text. Space OCR is designed to turn documents into structured data with per-value bounding boxes, so each extracted value can be verified against the original image and queried later as rows in a sheet.

Can the AI make coordinates up?

No. The page says coordinates come from the OCR pass, not from the language model. Extracted values are cross-checked, and uncertain results can be flagged with text_verified and needs_review.

What happens when it reads something wrong?

When the cross-check does not agree, the value is flagged for review rather than quietly accepted. The page also says uncertain values return needs_review, and the original image stays available for inspection and inline correction.

Can it handle line items and tables?

Yes. The product states that it can handle line items and tables, and that structured fields can be unfolded into rows that stack into a sheet you can query and export.

Quick Facts

Category
Developer Tool
Primary use
Document OCR and structured data extraction
Interfaces
Browser app, REST API, Claude Code plugin/skill, MCP endpoint
Output formats
Fields, Markdown, text
Website
space-ocr.com
Pricing
Free tier available; paid usage and subscriptions listed