Sanaf AI
Start free
Developer Tools

Nutrient Document Web Services API, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Nutrient Document Web Services API account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 12 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Nutrient Document Web Services API is

Process, convert, OCR, redact, sign, and analyze documents with Nutrient Document Web Services.

You paste in a key from your own Nutrient Document Web Services API account. It is kept encrypted, and you can withdraw it from inside Nutrient Document Web Services API whenever you like.

How a run works

One message in, the work done in Nutrient Document Web Services API.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Nutrient Document Web Services API. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Nutrient Document Web Services API account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

12 tools it already has

What it can do in Nutrient Document Web Services API

These are the ready-made tools your AI employee already has in Nutrient Document Web Services API. It is not limited to them, but it never has to be taught these.

  • Analyze Build CostEstimate the credits and Processor features required by Build API instructions without executing the document job or consuming credits.
  • Build DocumentSynchronously create one document from remote files, remote HTML, new pages, and composable safe actions, returning its filename, media type, and Base64 content up to 4 MB. Use thi
  • Convert Markdown to PDFConvert CommonMark or GitHub-Flavored Markdown text into a PDF using optional built-in styling, custom CSS, page layout, and syntax highlighting settings. Returns the filename, med
  • Create JWT TokenCreate a short-lived restricted Nutrient bearer token. This compatibility tool returns secret credential material; revoke it with REVOKEJWTTOKEN when it is no longer needed. Prefer
  • Create PDF from Web PageRender an HTML web page at a public URL, with optional page layout settings, into a PDF. Returns the filename, media type, and Base64 content up to 4 MB. This consumes Processor cr
  • Get Account InformationReturn the connected Nutrient account's subscription type, status, and estimated remaining credits.
  • Get Processor UsageReturn the connected account's Processor subscription status and credit usage counters.
  • Make PDF AccessibleAuto-tag a PDF at a remote URL for PDF/UA screen-reader accessibility and return the result's filename, media type, and Base64 content up to 4 MB. This consumes Processor credits;
  • OCR PDFApply optical character recognition to a PDF at a remote URL and return a searchable PDF's filename, media type, and Base64 content up to 4 MB. This consumes Processor credits; che
  • Revoke JWT TokenImmediately revoke a bearer token created by CREATEJWTTOKEN using its ID. Use this when a generated token is no longer needed or may be compromised.
  • Stage PDF RedactionsFind matching content in a remote PDF and return a review PDF's filename, media type, and Base64 content up to 4 MB with unapplied redaction marks. This action cannot permanently a
  • Watermark PDFAdd a positioned text or image watermark to every page of a PDF at a public URL and return the copy's filename, media type, and Base64 content up to 4 MB. This consumes Processor c
Access, and who is in charge of it

You stay the boss of your Nutrient Document Web Services API account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Nutrient Document Web Services API account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Nutrient Document Web Services API is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Nutrient Document Web Services API and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Nutrient Document Web Services API

Can an AI employee really work inside Nutrient Document Web Services API?
Yes. It signs in to your own Nutrient Document Web Services API account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Nutrient Document Web Services API?
No. Nothing moves and nothing is replaced. Your records stay in Nutrient Document Web Services API, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Nutrient Document Web Services API account?
You paste in a key from your own Nutrient Document Web Services API account. It is kept encrypted, and you can withdraw it from inside Nutrient Document Web Services API whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Nutrient Document Web Services API?
It has 12 ready-made tools in Nutrient Document Web Services API today, among them Analyze Build Cost, Build Document and Convert Markdown to PDF. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Nutrient Document Web Services API and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Nutrient Document Web Services API and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Nutrient Document Web Services API?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Nutrient Document Web Services API is written down with what it did and when.