Nutrient Document Web Services API MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with Nutrient Document Web Services API MCP or direct API to convert documents, run OCR, redact sensitive data, and apply signatures through natural language.

Nutrient Document Web Services API logoNutrient Document Web Services API
Api Key

Nutrient Document Web Services API is a cloud document processing service for converting, OCRing, redacting, signing, and analyzing files. Use it to automate complex PDF and document workflows without running document infrastructure yourself.

11 Tools

Try Nutrient Document Web Services API now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
Nutrient Document Web Services API
Try asking
TOOLS

Supported Tools

Every Nutrient Document Web Services API action and event your agent gets out of the box.

Analyze Build Cost

Estimate the credits and Processor features required by Build API instructions without executing the document job or consuming credits.

Build Document

Synchronously 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.

Convert Markdown to PDF

Convert CommonMark or GitHub-Flavored Markdown text into a PDF using optional built-in styling, custom CSS, page layout, and syntax highlighting settings.

Create PDF from Web Page

Render an HTML web page at a public URL, with optional page layout settings, into a PDF.

Get Account Information

Return the connected Nutrient account's subscription type, status, and estimated remaining credits.

Get Processor Usage

Return the connected account's Processor subscription status and credit usage counters.

Make PDF Accessible

Auto-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.

OCR PDF

Apply 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.

Revoke JWT Token

Immediately revoke a bearer token created by CREATE_JWT_TOKEN using its ID.

Stage PDF Redactions

Find 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.

Watermark PDF

Add 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.

SETUP GUIDE

Connect Nutrient Document Web Services API MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["nutrient_document_web_services_api"],
  mcp: true,
});
Create a session scoped to Nutrient Document Web Services API and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Convert the uploaded contract PDF to searchable text with OCR and summarize the key terms",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a Nutrient Document Web Services API request
SETUP GUIDE

Connect Nutrient Document Web Services API API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["nutrient_document_web_services_api"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to Nutrient Document Web Services API
3

Run Nutrient Document Web Services API tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Convert the uploaded contract PDF to searchable text with OCR and summarize the key terms" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the Nutrient Document Web Services API tool calls through the session, and print the final answer

Why Use Composio?

AI Native Nutrient Document Web Services API Integration

  • Supports both Nutrient Document Web Services API MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable document processing tool execution
  • Rich coverage for converting, OCRing, redacting, signing, and analyzing documents

Managed Auth

  • Secure API key handling so agents don't need hard-coded Nutrient Document Web Services credentials
  • Central place to manage, scope, and revoke Nutrient Document Web Services API access
  • Per user and per environment credentials for safer document automation workflows

Agent Optimized Design

  • Tools are shaped for AI agents, so document tasks like OCR, redaction, and conversion are easier to call correctly
  • Comprehensive execution logs show which document action ran, when it ran, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access Nutrient Document Web Services API
  • Scoped, least privilege access for sensitive PDF, contract, invoice, and form workflows
  • Full audit trail of document processing actions to support review and compliance
FAQ

Frequently asked questions

Yes, Nutrient Document Web Services API requires you to configure your own API key. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your Nutrient Document Web Services API connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your Nutrient Document Web Services API account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the Nutrient Document Web Services API actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside Nutrient Document Web Services API at any time.

When you connect a Nutrient Document Web Services API account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in Nutrient Document Web Services API as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside Nutrient Document Web Services API. If Nutrient Document Web Services API lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside Nutrient Document Web Services API at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each Nutrient Document Web Services API connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment Nutrient Document Web Services API rejects the old key. Create a new key in Nutrient Document Web Services API and reconnect the account from the Composio dashboard or by asking your agent to reconnect Nutrient Document Web Services API. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal Nutrient Document Web Services API use. Paid plans add higher limits and team features. Your Nutrient Document Web Services API plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple Nutrient Document Web Services API accounts).

With Composio, you connect Nutrient Document Web Services API once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with Nutrient Document Web Services API.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Nutrient Document Web Services API tool your agent needs.Free to start.

Start building