Where to Find Nutrient's SDKs, APIs, Code Examples, and AI Assistant
Nutrient's site is organized around a few entry points: a search bar, an "Ask AI" assistant, a code examples section, and product pages for its PDF SDKs, document APIs, and workflow automation. Developers evaluating the platform should start with the code examples and API documentation; enterprise buyers should start with the workflow automation and pricing pages. The site's own framing is that it is a "deterministic document platform for agents and humans," with auditable output and human review, and it states it is trusted by 3,000+ enterprises.
The main entry points on nutrient.io
The page evidence shows a navigation pattern built around four actions:
- Search — a general site search for finding pages by keyword.
- Ask AI — an assistant interface for asking questions about the platform.
- Code Examples — a dedicated section for implementation samples.
- Results — the output area where search or assistant responses appear.
If you land on the homepage and aren't sure where to go, these four controls are the fastest way to route yourself to the right resource.
For developers: SDKs, APIs, and code examples
Nutrient positions itself as offering "PDF SDKs, document APIs, and workflow automation." For a developer, the practical path is:
- Use Code Examples to see how a specific task is implemented before reading full documentation.
- Use Search with a concrete term (for example, a format conversion or a document-processing task) to jump to the relevant SDK or API page.
- Use Ask AI when you have a question that doesn't map cleanly to a page title — for example, which API surface handles a particular step in a workflow.
The site's messaging emphasizes that "the first 75 percent got easy" and "the last 25 percent is where you want Nutrient" — a signal that the platform is aimed at the hard edge cases of document processing rather than only basic conversion.
For enterprise buyers: workflow automation and pricing
If you're evaluating Nutrient commercially rather than building with it, the relevant pages are separate from the developer resources:
| Goal | Where to go |
|---|---|
| Understand what the platform covers end to end | "One platform, the whole document workflow" section |
| See workflow automation use cases | Workflow automation solution pages (e.g., Purchase Requisition) |
| Find commercial terms | The Pricing page under workflow automation |
The site lists a Pricing link at nutrient.io/workflow-automation/pricing/ and a Purchase Requisition solution page at nutrient.io/workflow-automation/solutions/purchase-requisition/. These are the documented starting points for pricing and purchase-related questions. The available material does not specify price levels, plan tiers, or whether a login is required to view them — check the pages directly rather than assuming free access.
Using the AI assistant to explore capabilities
The "Ask AI" control is the site's own tool for exploring what the platform does without knowing the exact page name. It's most useful when:
- You know the outcome you want ("extract data from invoices") but not which product handles it.
- You want to compare whether a task belongs to the SDK, the API, or workflow automation.
- You're scoping a workflow and need to know which parts Nutrient covers.
Because the site describes itself as "deterministic by design, governed for the enterprise," questions about auditability and human review are reasonable things to direct at the assistant or to the relevant product page.
Choosing your starting point
- You're a developer building an integration → Code Examples, then Search for the specific API or SDK.
- You're scoping a document workflow → the "One platform, the whole document workflow" section, then Ask AI for gaps.
- You need commercial terms → the Pricing page under workflow automation.
- You have a use case in mind (e.g., purchase requisitions) → the matching solution page, such as the Purchase Requisition page.
The site's core claim — "Your critical document workflows can't run on a guess" — frames the whole platform around reliability rather than novelty, which is worth keeping in mind when deciding whether to evaluate it against a simpler conversion tool.