Agencies & freelance developers
One endpoint you can resell across every client, whatever their documents look like
Client A wants purchase orders. Client B wants shipping manifests. Client C wants insurance claim forms. With a template-based parser each of those is a separate configuration project you have to build, bill for, and then maintain for years.
With Fieldcast the difference between those three clients is the contents of one array. Same endpoint, same integration code, different field names. What you built for the first client is most of what you ship to the third.
What the call looks like
The fields below are an example for this use case. Yours can be any names you like, up to 40 per call.
{
"fields": [
"po_number",
"vendor",
"ship_to",
"delivery_date",
"total_units",
"incoterms"
]
}And what comes back:
{
"po_number": "PO-55120",
"vendor": "Northwind Trading Co.",
"ship_to": "Warehouse 4, Rotterdam",
"delivery_date": "2026-09-02",
"total_units": 1840,
"incoterms": "DAP"
}Why the details matter here
Onboarding a client is a config change, not a project
No parser to draw, no model to train, no per-client setup fee you have to justify. The margin on the second client is much better than on the first.
Your integration code stays identical
One request shape, one response shape. You write the error handling, retry logic and queueing once and reuse it across the whole client book.
Predictable cost per client
One extraction per call regardless of how many fields that client wants or how many pages the document has. Easy to price a retainer against.
What it does not do
- There is no white-label or reseller programme yet. You would be integrating an API, not rebranding a product.
- There is no per-client dashboard, usage split, or sub-account structure — usage is tracked against one API key.
- No OCR for scanned documents yet.
- No SLA. It is a beta run by one developer, which matters if you are signing client contracts against it.
Listed plainly so you find out now rather than after integrating.
Questions
Can I put my own margin on top?
Nothing stops you billing your client for the workflow you build. But there is no formal reseller agreement or white-label tier today, so do not promise a client something the terms do not cover.
How do I separate usage per client?
Today you cannot — one key, one counter. If you need per-client attribution you would have to track it on your side. Multiple keys are a reasonable request; email me if you need it.
What if it gets a field wrong for a client?
Validate before you write. Fieldcast returns null rather than inventing values, but it does not guarantee the values it does return. For client work, put a review step on anything financial.
Test it on your own documents
Free tier is 50 extractions a month, no card, no sales call. That is deliberately enough to check accuracy on real files before you commit to anything.
Read the quickstart