NDNCI automation
Run Tools, follow jobs, and manage workspace resources with REST and MCP.
NDNCI's REST API lets your scripts and applications use the same authorized server operations as your workspace. MCP makes those operations available to compatible assistants through a standard protocol. Both share the workspace's credits, queues, permissions and weighted usage limits.
Use REST at https://api.ndnci.com/v1. Connect MCP clients to https://api.ndnci.com/mcp.
Start with a workspace and a key
Create a scoped access key, select its allowed workspaces, and discover the operations available to it. A key can authorize REST, MCP, or both. Set monetary spending ceilings and optional IP restrictions before connecting an unattended script.
Every call selects a workspace explicitly. Personal workspaces and organization workspaces keep their own credit pools, media, queues and limits.
What you can automate
- Discover permitted server Tool operations and inspect their input contracts.
- Estimate and run operations, then read, cancel or retry eligible jobs.
- Follow progress through polling, signed webhooks, or Pro server-sent events.
- Read queue capacity, credit allocations, expiration dates, transactions and usage.
- List, upload and download workspace media.
Browser-only Tools remain local. Direct media deletion and account administration are outside the public automation contract.
Find the contract you need
The API reference contains the actual endpoint contracts generated from OpenAPI. The MCP guide explains client connection and authorization. Read usage and budgets before creating a long-running automation.
Download the OpenAPI 3.2.1 document to generate a client or validate integration requests.