Schema and hostile input
Unexpected properties, prompt injection, oversized bodies, false evidence, repeated requests and upstream failure.
AI extraction · Exact evidence · Human approval
FieldDoc turns delivery notes and work orders into structured records without hiding the original. Every populated field must point back to literal source text.
Run a documentWorking project / not client data
Model output is only a proposal. The API validates a closed schema, clears any value whose evidence is not an exact substring, checks totals with deterministic code and keeps export behind a review step.
Inspect the architecture ↓Try it · Scenario · Trace
DELIVERY NOTE DN-2041 Date: 2026-07-12 Supplier: Bay Parts LLC Customer: Harbor Dental Order: PO-88 Currency: USD 1 x Filter pack @ $120.00 = $120.00 Subtotal: $120.00 Tax: $8.40 Total: $128.40
Choose a sample or paste a document, then analyze it. Results always remain proposals until you approve them.
Architecture / bounded by design
Same-origin requests, strict content type, 8,000-character input cap, rate limits and no public API key.
A low-cost model returns one closed schema. The document is explicitly treated as untrusted data.
Every populated field needs an exact excerpt. A server-side post-validator clears anything that cannot be located.
Totals and duplicate checks are deterministic. Export unlocks only after an explicit source comparison.
Acceptance matrix
Unexpected properties, prompt injection, oversized bodies, false evidence, repeated requests and upstream failure.
Load, compare, correct, approve and export while every decision remains visible in the same workspace.
Three labelled samples, a single primary action, plain statuses and a recovery path that never destroys the original.
Need document work to stop at “review,” not at “magic”?