Connect Codex to Nutrient Document Web Services API
Set up in minutes
Choose where it runs
On your computer through your own Codex, or hosted in the cloud. The rest of setup adapts to your choice:
Pick what it can do in Nutrient Document Web Services API
A preset of real Nutrient Document Web Services API operations. Each one becomes a tool the agent can call, and it can't touch anything outside the list.
Connect Nutrient Document Web Services API
One sign-in. The agent acts through your account, scoped to the operations you picked.
Add your personal MCP link
The last step mints a private MCP URL for this agent and walks you through exactly this, with your real link filled in. The page flips to Connected the moment your Codex first calls in. Codex connects when a session starts — run codex, or restart a running one (in the Codex app, Restart).
Run this in your terminal. The Codex app shares its config, so it gets the server too
<your-link> is your personal server URL — setup mints it for you.
Tools Codex gets
Nutrient Document Web Services API
24 toolsGet account information.
Get usage for a product.
Parse document structure.
Parse document structure asynchronously.
Extract structured data from documents.
Extract structured data from documents asynchronously.
Retrieve a stored processing run.
Delete a stored processing run.
Cancel a queued or running processing run.
Split a merged document into sub-documents.
Split a document asynchronously.
Classify a document.
Classify a document asynchronously.
List batches.
Retrieve a batch.
Cancel a batch.
List processors.
Create a processor.
Get a processor.
Rename a processor.
Delete a processor.
Create a processor version.
Get a processor version.
Publish a processor version.
About Codex
Frequently asked questions
More ways to connect
More tools for Codex
Use Nutrient Document Web Services API with other agents
Open your Codex agent in one click.
NoClick runs Codex for you with Nutrient Document Web Services API wired in as tools. Connect your account and run.