Nutrient Document Web Services API for AI agents
Nutrient Document Web Services is a document-processing API for converting, OCR-ing, redacting, watermarking, and signing files like PDFs. Development teams embed it to handle document workflows at scale. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Nutrient Document Web Services API.
Convert a markdown file to PDF
Turn a markdown report into a formatted PDF ready to send to a client or stakeholder.
Run OCR on a scanned PDF
Extract searchable text from a scanned contract so its contents can be indexed or reviewed.
Stage redactions before applying
Preview proposed redactions on a sensitive PDF for approval before the changes are made final.
13 Nutrient Document Web Services API actions, graded by risk.
Every Nutrient Document Web Services API action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
5Look things up. Allowed by default.
- nutrient_document_web_services_api.get_account_infoGet Account Information
- nutrient_document_web_services_api.get_processor_usageGet Processor Usage
- nutrient_document_web_services_api.analyze_buildAnalyze Build Request (Deprecated)
- nutrient_document_web_services_api.analyze_build_costAnalyze Build Cost
- nutrient_document_web_services_api.convert_markdown_to_pdfConvert Markdown to PDF
write
7Create and change things. Allow, or ask the user first.
- nutrient_document_web_services_api.create_jwt_tokenCreate JWT Token
- nutrient_document_web_services_api.create_pdf_from_web_pageCreate PDF from Web Page
- nutrient_document_web_services_api.ocr_pdfOCR PDF
- nutrient_document_web_services_api.watermark_pdfWatermark PDF
- nutrient_document_web_services_api.build_documentBuild Document
- nutrient_document_web_services_api.make_pdf_accessibleMake PDF Accessible
- nutrient_document_web_services_api.stage_pdf_redactionsStage PDF Redactions
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- nutrient_document_web_services_api.revoke_jwt_tokenRevoke JWT Token
Nutrient Document Web Services API in three steps.
- 01Your users connect Nutrient Document Web Services APIThey add their Nutrient Document Web Services API api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create JWT Token” can wait for the user, and “revoke JWT Token” can be denied outright.
- 03Any agent can actYour agent calls Nutrient Document Web Services API through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('nutrient_document_web_services_api', { read: 'allow', write: 'ask', // create_jwt_token destructive: 'deny', // revoke_jwt_token }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Nutrient Document Web Services API connects.
Users add their Nutrient Document Web Services API api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Nutrient Document Web Services API connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Nutrient Document Web Services API from any agent.
Nutrient Document Web Services API and Arc0, answered.
Can I use Nutrient Document Web Services API with Claude, ChatGPT or Cursor?
Yes. Connect Nutrient Document Web Services API to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Nutrient Document Web Services API actions you allow.
How do users connect Nutrient Document Web Services API?
Users add their Nutrient Document Web Services API api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Nutrient Document Web Services API actions can my agent take?
13 in total: 5 read, 7 write and 1 destructive, such as “create JWT Token”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Nutrient Document Web Services API?
Yes. Actions like “revoke JWT Token” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Nutrient Document Web Services API too?
Yes. The same Nutrient Document Web Services API connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Nutrient Document Web Services API into your agent.
Your users connect Nutrient Document Web Services API once, under your brand. Your agent gets 13 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan