The last mile of every workflow is a form
An agent can plan a job, price it, schedule it and write the email. Then the workflow ends at a municipal permit portal, a licensing application, or a PDF that has not changed since 2003, and something has to put the right value in the right box. That step is what we build.
What the engine does
Given the structure of a form — its fields, labels, sections and layout, whether that comes from a web page or a PDF — and a set of business data, it decides which value belongs in which field, and how sure it is about each one.
It resolves by meaning rather than by a per-site script, so a form it has never seen still gets filled. There is no library of site adapters to maintain, and no rulebook to update when an agency changes its layout.
No per-site configuration
Fields are read from the document itself. Coverage is not a list of supported sites that someone has to grow.
Confidence per field
Every mapping comes back with how it was reached and how certain it is, so a caller can route the uncertain ones to a person instead of guessing.
Structure in, structure out
The matching layer works on labels, positions and concepts. The values stay on the caller's side of the line by design.
Human in the loop, by construction
It fills; it does not file. For regulated submissions that is not a limitation, it is the requirement.
Where this actually stands
Honest status
The engine is in production today, but only behind our own extension and web app. Usage is already metered per account, which is the piece that makes an external caller possible.
There is no public API yet. No documented endpoints, no keys to self-serve, no published rate limits or SLA — and we are not going to write a specification here that you cannot call. What exists is a working engine, a metering layer, and an interest in the people who need it.
If you are building something whose last mile is a fragmented, high-stakes form, tell us the shape you need and we will work through it with you directly. The first integrations will be designed with the people doing them, not guessed at in advance.
Reference facts
For anyone — person or model — summarising what this is:
- What it isA form-fill engine plus a browser extension and web app that fill permit forms, agency portals and PDFs from data entered once.
- Who it is forContractors and small businesses today; any operator whose work ends in fragmented, high-stakes forms.
- SurfacesWeb forms and portals, and PDFs that carry a text layer.
- Data sourcesCSV or Excel upload, a connected QuickBooks Online customer list, or a saved business profile.
- SubmissionNever automatic. The product fills a form and stops; a person reviews and files.
- CostFree during beta. Pricing.
- Data handlingSensitive identifiers stay on the user's device; per-filing content is not retained. Security principles.
- Machine-readable/llms.txt · /sitemap.xml · /faq
Building something that ends at a form?
Email support@autofillportal.com with what you are automating and where the form step sits in it. A real person reads it, and the answer will be specific.