Fieldry

Developers

One evidence format, every caller.

REST for control, MCP for agents, SDKs and n8n for speed. Sync ?wait, async 202, idempotency keys and X-Credits-Used everywhere.

Get Started

Call it your way

Pick a caller to see what the integration looks like.

POST /v1/extract?wait200

X-Credits-Used: 40header

REST API

POST file + schema, sync ?wait or async 202 with webhook. Idempotency keys, credits in headers.

  • ?wait sync ≤25s
  • Idempotency-Key
  • X-Credits-Used
Feature 1 of 3

Developers

Glue code. One call.

What changes when parsing, grounding and billing are one API.

After emphasis: 50%

BEFORE / DIY parsing
Raw OCR + prompt glue

Every team rebuilds parsing

Agents guessing numbers

No citations back

Polling job status

No webhook contract

Surprise invoices

No per-call cost header

AFTER / Fieldry callers

One POST, cited JSON

Fieldry

Minutes

Grounded tool calls

Fieldry

MCP

Webhooks + retries

Fieldry

Signed

Credits per call

Fieldry

Header
Same evidence format on every caller.

Inside Developers

REST APIUpload, ?wait sync mode, idempotency key.Explore MCP ServerClaude, ChatGPT, Cursor and Agent2Agent ready.Explore SDKs & WebhooksPython/JS, n8n node, webhook callbacks.Explore

Developers questions, answered

The questions teams ask most about developers.

Talk to us

One POST with file + schema returns cited JSON. SDKs wrap auth, retries and webhooks; n8n covers no-code. Most teams parse their first doc in minutes.

Via the MCP server: Claude, ChatGPT and Cursor list document tools and get value/confidence/evidence back — grounded answers with citations.

202 + job id, webhook on complete (signed, 5 retries), idempotency keys make retries safe. Batch uses the same shape at 50% credits.

Ship parsing this afternoon

REST, MCP, SDKs and webhooks.

An engineer POSTs an invoice after lunch; by standup the flow posts cited JSON to staging.

Request a DemoSee pricing