Every mailroom needs a good hire. This one sorts documents before you finish your coffee. 🐾📑 Nutrient’s classify tooling sorts incoming documents by type so the right document reaches the right team, without anyone sorting by hand.

What is the Nutrient Decision Model, and why would you ever use it over a large language model? Easy answer: cost and speed

Most questions you ask about a document have a short answer. Is this an invoice or a contract? Is this extracted value actually on the page? Where does one invoice end and the next begin? Yet the usual approach is to send the whole file to a general-purpose LLM and wait while it writes a reply, one token at a time. So we built something different: the Nutrient document decision model. It reads a document, both the page image and the text, and returns a choice plus a calibrated confidence score. No generated paragraphs, no waiting. What that gets you: → About 200 ms per answer → Scores calibrated to how often the model is actually right → Visual understanding that text-only approaches miss It’s already live in Nutrient DWS, powering our classify and split endpoints and checking extraction results against the source document. Nutrient AI engineer, Austin Nguyen, explains why we built it, how we trained it, and where it falls short: bit.ly/4jpIZyF Try the demo on Hugging Face: bit.ly/4i8tEjE

Story time: we gave our extraction a four-page California small claims form, and it came back with the currency as "USD," even though those three letters appear nowhere in the document. The form is a real court form filled in with test data, and we'd asked for six things: - The plaintiff - The defendant - Amount claimed - Currency - Date of the incident - Reason for the claim Five of them were right there on the page. The currency wasn't, but our setup mentioned that US court forms always use dollars, so the model did the sensible thing and filled in USD. It wasn't really wrong, but it was a guess rather than something read off the form, and in the extracted data it looked exactly like the five values that were. If you're automating claims, contracts or court filings, that's the kind of answer that slips through until someone has to explain where it came from. We caught it because every value comes back with a citation showing the page it came from and the exact spot on that page. The currency pointed to a different page from the amount it belonged to and scored noticeably lower, so a review step would send that one field to a person and let everything else through. And that's really what we want from AI on such documents. It doesn't have to be perfect, but it does need to alert a human when it is not exceptionally confident in a result. Remember, you are responsible for every document you submit - whether AI assisted or not, so you better be sure that it is correct. Don't play AI roulette. See the full walkthrough: bit.ly/4zwT8OJ

A picture of a signature on a PDF doesn't tell anyone whether the contract changed after it was signed. A digital signature does, because any later change to the signed content shows up when the file is checked. How to add one with Nutrient API: bit.ly/4s1GowY

Building on the Nutrient Data Extraction API is a breeze. Our customer came to us with a problem: they receive invoices from all across the globe. Different languages, different currencies, and each one checked by hand. Not anymore. In less than 30 minutes, we built them a custom app that identifies discrepancies, and notifies their accounts team when something needs their attention. All built inside of Claude using only natural language.

An expense report can spend far more time waiting in inboxes than it ever spends being reviewed. It goes to a manager, then finance, then a VP if it's over $10,000, and every handoff is another inbox where it can sit over a weekend while the contract waits to be paid. Nutrient Workflow sends it to the right person the moment it's submitted, nudges reviewers automatically, moves it to a backup approver if someone doesn't act in time, and pushes the approved numbers into your finance system so nobody retypes them. We save you time, and time is money. Expense that here: bit.ly/4yKWayY

It's only a matter of time before a major incident gets blamed on a mistake made by an AI agent, and "the AI did it" is an excuse nobody is going to accept. Each of us is responsible for what our agents produce. That makes auditability more important than it has ever been, especially now that AI is drafting redlines, discharge summaries, and responses that people then sign off on. With Nutrient Document Authoring, each AI suggestion lands as a tracked change with a comment explaining it, so a human is always aware of what is happening, and can approve changes on a case-by-case basis. An instrumental tool in high leverage situations. Call it CYA for the age of AI agents. The AI won't be the one sitting in the incident review when something goes wrong, but you will, so bring the receipts. Learn more: bit.ly/3WeiFxK

If you can't trust your OCR some of the time, can you trust it at all? OCR turns a scan or photo of a page into text your software can use. Clean, typed pages are a breeze. Real documents aren't. A rotated scan, small print, a long table, a handwritten form: that's where a number gets misread or lands in the wrong row. And the response still looks fine. Your agents can't tell. If you aren't looking closely, you won't either. But someone still has to sign off on it. So the question isn't whether OCR works on an easy page. It's whether you can tell when it got something wrong. We compared nine OCR APIs, including ours, and we didn't pull any punches. The results might surprise you. Nutrient links extracted content back to where it appears on the page and marks the values that need a second look, so you know what to check. Read more: bit.ly/4rQppOj

For nine days in April, our monitoring vendor had our metrics switched off, and the only reason we noticed was that our dashboards looked suspiciously calm. There was no email or status-page notice, no alerts. And losing metrics silently can be worse than a clear outage because alerts can't fire on data that never arrives. We ended that service, and because everything was already instrumented with OpenTelemetry and routed through collectors we run ourselves, moving terabytes of telemetry to a new vendor took a handful of config changes and no application redeploys. The lesson for businesses is simple. Build on the standard, not the vendor, and pivoting will cost you very little. Thank you @dash0hq! bit.ly/4hJ2RKJ

You don't hand an AI agent autonomy. It earns it. SpaceXAI Engineer Lauren Tan (@poteto), who ships thousands of code changes a month with AI agents, puts it simply: "Make loops autonomous only after it earns your trust." The agents have to show their work, and any step can stop the work when something looks off. The same is true when the agent works on your documents instead of your code. Before an AI agent fills a form or redacts a clause in a real contract, someone has to sign their name off. The trust comes down to three answers about your docs: who set it up, what permissions the agent has, and has anything changed? Nutrient AI Assistant 2.4.0 keeps those answers on file: • Every agent's setup is saved and versioned, so you know exactly which version ran on any given day. • Edits can wait for a person's approval, so someone can stop the line before anything changes. • Each session reaches only the documents and agents it was issued for, and narrow jobs can go to helpers that can only read. Start with relatively strict permissions. Loosen them as the agent proves itself, and keep records of every change. How it works: bit.ly/4rN1O0M

Great question! Yes, Nutrient supports document comparison, annotations, version history, and audit trails, so you can build redlining-style workflows that show what changed, who changed it, and when. Learn more at nutrient.io

In AI-powered workflows, document infrastructure isn't just a supporting feature. It's fundamental. When AI prepares a tax return, accountants still need to check it. That means tracing every number back to its source, checking the calculation, and marking up what needs attention, all inside the platform instead of across a patchwork of tools. That's the approach Current took when building their AI-native tax platform on Nutrient. "This product wouldn't work without document editing," says @tuckerhaas, CTO at Current. Read the story 👇 bit.ly/3VYoY8u

An AI-generated fact is only useful to a legal practitioner if they can verify it. Page helps VA disability firms review case files that can run to tens of thousands of pages. With Nutrient Web SDK, practitioners can move from AI-extracted information directly to the underlying source document, with viewing, annotations, and form filling directly inside the platform. For Page’s engineers, that means more time building the product and less time maintaining infrastructure. Read how Page built its document experience → bit.ly/46DAf0g