Developers
Everything the console does, the API does. Three doors: an MCP server your assistant can call, a REST API your code can call, and the SDK story for what to reach for today.
MCP
The console is an MCP server. Point Claude Code, or any MCP client, at it and it can turn a sentence into a validated business process, search the agent catalogue, explain a failure and read vendor docs, all inside your tenant.
API
A JSON API behind a personal access token: business processes, versions, runs, deployments, connectors, members and the drafting assistant itself.
SDK
There is no packaged SDK yet; the API is small enough to call directly and the MCP door covers agents. What to use now, in JavaScript and Python, and what is planned.
Where things live
| Host | https://console.dev.ductileai.com today; a production host follows the same paths. |
|---|---|
| MCP server | POST /mcp, JSON-RPC 2.0, protocol 2026-07-28 |
| REST API | /api/v1/console/… |
| Authentication | a personal access token, Authorization: Bearer dpt_…, minted in the console under Settings › Tokens |
| Tenancy | every call acts inside the token owner's tenant, with that person's permissions; a token can do nothing its owner cannot |
Before your first call
- Sign in to the console and open Settings › Tokens.
- Mint a token with a name and, if you like, a shorter life. The value is shown once; only its hash is kept.
- Send it as
Authorization: Bearer dpt_…. A token cannot mint tokens, cannot step up, and cannot change sign-in settings: those doors need a person at the console.
Sample data first. Every agent ships sample records, and a process runs on those before anything real is connected. The MCP tools and the API both honour that: nothing here reaches a vendor until a connection is named and the process is deployed.