Skip to content
actionlake
Start free

Connectors · Files & documents

Nutrient DWS Processor API MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Nutrient DWS Processor API and the rest of your systems. It gives your agent 8 Nutrient DWS Processor API actions (5 reads, 2 writes and 1 that wait for a confirmation) and holds the Nutrient DWS Processor API credential itself, so the agent never does. It paces Nutrient DWS Processor API's limits and records every call.

Connect Nutrient DWS Processor API freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "nutrient_dws.account.get",  intent: "check which Nutrient DWS Processor API account is connected"}# Get account information · read · 1 upstream call
  • 8actionsin one signed file
  • 5readlook, never change
  • 2writecreate and update
  • 1wait for a yesdestructive, confirmed first

Set up

Connect Nutrient DWS Processor API in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Nutrient DWS Processor API.

    Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key.

    • api_keyNutrient DWS Processor API key: dashboard.nutrient.io > API keys (live key)
    account { op: "connections.requirements", service: "nutrient_dws" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "nutrient_dws.account.get" }# get account information · read · 1 upstream callcheck { action: "nutrient_dws.build_jobs.create", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Nutrient DWS Processor API at a glance

Sign-in
Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead.
You provide
api_key
Limits we pace to
50 calls per 10 seconds, per connection
API covered
DWS Processor API 1.19.0 (OpenAPI 3.1)api.nutrient.io
Built from
Nutrient DWS Processor API's documentation, read 23 October 2026nutrient.io
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
3 of 5 reads, for up to 5 minutes; a write clears what it affects
Shared entities
1, so ask can line Nutrient DWS Processor API up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Nutrient DWS Processor API.

8 actions in 7 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 5readlook, never change
  • 2writecreate and update
  • 1destructivewait for a confirmation

  1. Tokens

    2

    0 read · 1 write · 1 destructive

    Generate an API token · Revoke an API token

  2. Account

    1

    1 read · 0 write · 0 destructive

    Get account information

  3. Account usage

    1

    1 read · 0 write · 0 destructive

    Get usage for a product

  4. Async jobs

    1

    1 read · 0 write · 0 destructive

    Get an async job's status

  5. Build analyses

    1

    1 read · 0 write · 0 destructive

    Analyze a build request's credit cost

  6. Build jobs

    1

    0 read · 1 write · 0 destructive

    Submit an async Build API job

  7. Document contents

    1

    1 read · 0 write · 0 destructive

    Extract document contents as JSON

Top actions

The Nutrient DWS Processor API API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems.

ActionWhat it doesEffectSame name in
nutrient_dws.build_jobs.createSubmit an async Build API jobSubmit an async Build API job.writethis connector
nutrient_dws.document_contents.queryExtract document contents as JSONExtract document contents as JSON.readthis connector
nutrient_dws.account.getGet account informationGet account information.readthis connector
nutrient_dws.async_jobs.getGet an async job's statusGet an async job's status.readthis connector
nutrient_dws.account_usage.getGet usage for a productGet usage for a product.readthis connector
nutrient_dws.tokens.createGenerate an API tokenGenerate an API token.writethis connector
nutrient_dws.build_analyses.queryAnalyze a build request's credit costAnalyze a build request's credit cost.readthis connector
nutrient_dws.tokens.deleteRevoke an API tokenRevoke an API token.destructivethis connector

Try it

Prompts to paste into Claude.

Each one names the Nutrient DWS Processor API actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Get account information in Nutrient DWS Processor API and tell me what stands out.

    callsnutrient_dws.account.get

  2. Writewrite

    Submit an async Build API job in Nutrient DWS Processor API. Show me exactly what you will send before you save it.

    callsnutrient_dws.build_jobs.create

Governance for Nutrient DWS Processor API

Destructive actions wait for a yes.

1 Nutrient DWS Processor API action is destructive. This is it:

  • Revoke an API tokennutrient_dws.tokens.delete

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

donutrient_dws.tokens.deleteconfirm_policy: human

Revoke an API token?

intent: the user asked me to revoke an API token

run suspended · waiting for a named person · key nutrient-dws-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "nutrient-dws-agent",  allowed_actions: ["nutrient_dws.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "nutrient_dws.tokens.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Nutrient DWS Processor API only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Nutrient DWS Processor API costs on actionlake.

Every Nutrient DWS Processor API action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Nutrient DWS Processor API refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 8 Nutrient DWS Processor API actions
  • 8actions pageeach page of a long list is one call
  • 3reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Nutrient DWS Processor API action.

8 actions by area: the id your agent calls, what it does, and its effect.

Tokens2
  • nutrient_dws.tokens.createGenerate an API tokenwrite
  • nutrient_dws.tokens.deleteRevoke an API tokendestructive
Account1
  • nutrient_dws.account.getGet account informationread
Account usage1
  • nutrient_dws.account_usage.getGet usage for a productread
Async jobs1
  • nutrient_dws.async_jobs.getGet an async job's statusread
Build analyses1
  • nutrient_dws.build_analyses.queryAnalyze a build request's credit costread
Build jobs1
  • nutrient_dws.build_jobs.createSubmit an async Build API jobwrite
Document contents1
  • nutrient_dws.document_contents.queryExtract document contents as JSONread

Questions

The Nutrient DWS Processor API MCP server, answered.

Is there a Nutrient DWS Processor API MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 8 Nutrient DWS Processor API actions across tokens, account, account usage and async jobs, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Nutrient DWS Processor API.

What do I need to connect Nutrient DWS Processor API?

Nutrient DWS Processor API key: dashboard.nutrient.io > API keys (live key). The free call account { op: "connections.requirements", service: "nutrient_dws" } lists exactly what to paste.

Can an AI agent delete or change things in Nutrient DWS Processor API?

Only if its key allows it, and only with an explicit confirmation. 1 Nutrient DWS Processor API action is destructive, including revoke an API token. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Nutrient DWS Processor API API limit?

actionlake paces every call to the limits in the Nutrient DWS Processor API service file: 50 calls per 10 seconds per connection. Repeated reads are answered from cache (3 Nutrient DWS Processor API actions can be), which never reaches Nutrient DWS Processor API.

What does a Nutrient DWS Processor API action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (8 Nutrient DWS Processor API actions page). Cache hits, searches, dry runs and calls Nutrient DWS Processor API refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Nutrient DWS Processor API API does it cover?

The DWS Processor API 1.19.0 (OpenAPI 3.1) at api.nutrient.io. It is built from Nutrient DWS Processor API's documentation as read on 23 October 2026. 8 actions in 7 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Nutrient DWS Processor API data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Nutrient DWS Processor API credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Nutrient DWS Processor API

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Nutrient DWS Processor API; the name is the vendor's own. Counts are from the Nutrient DWS Processor API service file, version 1.0.0.

Give your agent Nutrient DWS Processor API today.

Connect Nutrient DWS Processor API freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.