Backed by
Combinator
Interfaze vs Extend
Your fields in one call, about twice as fast.
One request returns structured JSON with a bounding box and a confidence score for every word, and the same API reads documents, audio and video.
Trusted by builders at
Why teams choose Interfaze over Extend
About twice as fast and 3.5 times cheaper on the same documents, audio and video next to your PDFs, and a lead on the public olmOCR benchmark.
Interfaze vs Extend on the same document
Same pages and same fields, sent to both APIs. Three selected pages where interfaze-1 read a field Extend got wrong. Pick one to see where each API placed its fields, or the JSON it returned.
Request form
Rotated table scan
Email printout
Boxes on the page
Returned JSON
correct value
wrong value, boxed where the API read it
○
not returned
Interfazeinterfaze-1structured JSON
11/11 field checks passed
✓
rjr_program_number
702919
0.99
✓
response_code
AM5
0.94
✓
project_name
Doral & Co. '98 Fringe 1 Free Carton Order Form
0.99
✓
quantity
539,000
0.99
✓
responders
161700
1.00
✓
days_offer_open
367
1.00
✓
agency_contact
Beverly Flichman
0.99
✓
agency_phone
(910) 992-9406
0.88
✓
age_verification
NO
0.88
✓
marketing_person
Deidra Thompkins
0.99
✓
form_footer
RJRT Form 991 - WML 9/25/97
Read correctly.
Extendextraction_operatorstructured JSON
10/11 field checks passed
✗
form_footer
RJRT Form 001 - WML 9/25/97 · page says RJRT Form 991 - WML 9/25/97
0.65
✓
rjr_program_number
702919
0.99
✓
response_code
AM5
0.98
✓
project_name
Doral & Co. '98 Fringe 1 Free Carton Order Form
0.65
✓
quantity
539,000
1.00
✓
responders
161700
1.00
✓
days_offer_open
367
0.95
✓
agency_contact
Beverly Flichman
0.94
✓
agency_phone
(910) 992-9406
0.96
✓
age_verification
NO
0.99
✓
marketing_person
Deidra Thompkins
0.99
One API call instead of a pipeline
Extend recommends async runs with polling or webhooks in production. With Interfaze one request returns the fields, audio included.
Document extraction
Claims intake
integration steps
1 call · 1 API
done first
4/4 steps · 2 APIs
done
Scanned form
Extract run
Poll run
Your code
Fields
Interfaze
One request
Fields + boxes
1 call · 1 API
first
4/4 steps · 2 APIs
done
Scanned form
Extract run
Poll run
Your code
Fields
Interfaze
Fields + boxes
Interfaze vs Extend benchmarks
Same 101 documents, same field list, first successful call to each API: how many came back fast, and how many cost under 3¢.
higher is better
Measure
Interfaze
Extend
Answered in under 20 s
share of documents, time per API call · 101 documents
84.2%
11.9%
Answered in under 30 s
share of documents, time per API call · 101 documents
93.1%
70.3%
Under 3¢ per document
share of documents at list prices · 101 documents
95.0%
0.0%
Interfaze vs Extend on olmOCR-bench
Scores from the public olmOCR benchmark. The overall ranking first, then the three tasks with the biggest gap.
Interfaze vs Extend, feature by feature
Checked against both companies' docs.
Interfaze
Extend
Classification and translation in one call
OCR, classification and translation in a single request
Classification and translation in one call
Classify is a separate endpoint; no translation in the API docs
Open weights
interfaze-1.1-lite runs on one 80 GB GPU
Open weights
Hosted only
One synchronous call
One request returns the JSON; streaming available
One synchronous call
Create a run, then fetch it: sync endpoints time out at 5 minutes, longer jobs need polling or webhooks
Multimodal input
Documents, images, audio and video
Multimodal input
Documents, images, spreadsheets and email; no audio or video in the supported file types
Multi-document Q&A
Send several documents in one request and ask questions across them
Multi-document Q&A
Multi-file extraction into fields; no question answering across documents in the docs
Cost per document
$0.023 on average across our 101 test documents
Cost per document
$0.08–0.10 per document on average at the listed credit rates
Speed per document
12.4 s median on our 101 test documents
Speed per document
26.2 s median on the same documents
olmOCR benchmark score
1st on olmOCR (85.7%)
olmOCR benchmark score
Extend Parse 2.0 at 80.8% on olmOCR
Bounding boxes with confidence scores
Every OCR word and line with pixel bounds and a 0–1 confidence, in every response
Bounding boxes with confidence scores
Word-level citations and per-field confidence
Standard SDKs
OpenAI Chat Completions compatible: OpenAI SDK, Vercel AI SDK, LangChain
Standard SDKs
Own SDKs (TypeScript, Python, Go)
How to migrate from Extend to Interfaze
The same extraction in Interfaze and Extend, side by side. Your existing schema works as is. Or let your coding agent make the switch.
Interfaze
OpenAI SDK
Vercel AI SDK
import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api.interfaze.ai/v1",
apiKey: process.env.INTERFAZE_API_KEY,
});
const res = await client.chat.completions.create({
model: "interfaze-1",
response_format: {
type: "json_schema",
json_schema: { name: "invoice", schema: INVOICE_SCHEMA },
},
messages: [{
role: "user",
content: [
{ type: "text", text: "Extract the fields" },
{ type: "file", file: { filename: "invoice.pdf",
file_data: pdfUrl } },
],
}],
});
const invoice = JSON.parse(res.choices[0].message.content);Extend
import { ExtendClient } from "extend-ai";
const extend = new ExtendClient({
token: process.env.EXTEND_API_KEY,
});
// Run an extractor built from your schema, then poll
const run = await extend.extractRuns.createAndPoll({
extractor: { id: EXTRACTOR_ID },
file: { url: pdfUrl },
});
const invoice = run.output.value;Interfaze vs Extend: common questions
What people usually ask before switching from Extend.
Send us your hardest PDF.
If we can't beat your current provider,
we'll give you $3,000 in credits.
Start for free. No credit card required.