Nutrient Document Web Services API

@Nutrient what would it cost in credits to merge these three contract PDFs, add a watermark, and flatten all the form fields?

Based on the Build API instructions you described, this job would consume approximately 45 credits. The breakdown: merging three documents (15 credits), applying a watermark to each page (20 credits), and flattening form fields (10 credits). Your account currently has 8,240 credits remaining on the Professional plan. This is an estimate only — the actual cost depends on page count and document complexity. No credits were consumed by this analysis.

This example uses the Analyze Build Cost tool to preview credit consumption before executing an expensive multi-step document operation. Useful for budget-conscious workflows where you need cost visibility upfront. Requires a valid API key with access to the Processor API; the estimate assumes typical document sizes and may vary by 10–15% in practice.

@Nutrient convert this markdown spec into a PDF with syntax highlighting and our brand CSS, then return the file so I can attach it to the release email.

I've converted your markdown specification to PDF using GitHub-Flavored Markdown parsing, applied syntax highlighting for the code blocks, and injected the custom CSS you provided. The resulting PDF is 12 pages, A4 portrait layout. File returned: technical-spec-v2.1.pdf (842 KB, Base64-encoded). This operation consumed 8 Processor credits. You can decode the Base64 content and attach it directly to your email client or upload it to your file storage.

This example demonstrates the Convert Markdown to PDF tool with custom styling. The MCP returns the full PDF as Base64 content (up to 4 MB), so you can immediately use it downstream without a separate download step. Be aware that large documents may hit the 4 MB response limit; for bigger files, consider using the asynchronous Build API instead.

@Nutrient check my account status and tell me if I have enough credits left to process 200 invoice PDFs this month with OCR and text extraction.

Your Nutrient account is on the Business plan, active and in good standing. You currently have 12,450 credits remaining this billing cycle (resets in 18 days). Processing 200 invoices with OCR and text extraction typically consumes 15–20 credits per document, so you'd need approximately 3,000–4,000 credits total. You have sufficient headroom for this batch. If you exceed your limit, overage billing applies at $0.02 per credit on your plan tier.

This example pairs the Get Account Information and Get Processor Usage tools with the AI's reasoning to answer a capacity-planning question. The credit-per-document estimate is illustrative and depends on page count, image resolution, and OCR complexity. Always test a sample batch first to refine your cost model before committing to large-scale processing.

When Nutrient wins for high-volume proposal assembly

A 6-person sales team closes 40 deals a month, each needing a custom contract PDF assembled from pricing tables, legal boilerplate, and client-specific terms. Nutrient's Build Document tool is the right call here because it composes multi-part documents from remote files and new pages in one synchronous call, returning Base64 content under 4MB without touching your filesystem. The Analyze Build Cost tool lets the team pre-flight each job to confirm credit usage before execution, which matters when you're burning through hundreds of documents monthly. The threshold: if your contracts regularly exceed 4MB or you need asynchronous processing for 100+ page documents, you'll hit the size ceiling and need a different approach. For typical B2B contracts under 50 pages, this MCP keeps document assembly inside your Switchy workspace without managing storage or webhooks.

Markdown-to-PDF for developer docs at ship time

A 3-person developer relations team ships SDK documentation every two weeks, converting 20-30 Markdown files into styled PDFs for offline distribution. Nutrient's Convert Markdown to PDF tool handles this cleanly because it supports GitHub-Flavored Markdown with syntax highlighting and custom CSS, returning ready-to-ship PDFs in one call. The team uses Get Account Information to monitor credit burn during release sprints when doc volume spikes. This works when your Markdown is already the source of truth and you need consistent styling across all outputs. The trade-off: if your docs include complex interactive examples or need per-page layout control beyond CSS, the Markdown converter won't cut it and you'll need the full Build Document tool or a different rendering stack. For straightforward technical writing that lives in Markdown, this is the fastest path from commit to PDF.

When web-to-PDF capture fits support ticket workflows

A 5-person support team handles 200 tickets a week, many requiring snapshots of customer-reported UI bugs or configuration screens for internal tracking. Nutrient's Create PDF from Web Page tool is borderline here: it renders public URLs into PDFs with layout control, which works for capturing external dashboards or public-facing pages customers reference. The Get Processor Usage tool helps the team track credit consumption against their monthly budget. The limitation is the 'public URL' requirement—if your support flow involves authenticated customer portals or localhost screenshots, this MCP can't reach them and you need a browser automation tool instead. For support teams triaging issues on public SaaS interfaces or documentation pages, this keeps visual evidence inside Switchy without managing headless Chrome. If more than 30% of your captures need auth, skip this and use Playwright or Puppeteer.