Developers
Developer integrations
Choose HTTP API, SDK, CLI, MCP or local Agent Skills, and distinguish integration from deployment.
Updated
Use the console for everyday creative work. Developer entries support scripts, external agents and managed execution environments.
| Need | Interface |
|---|---|
| Call business capabilities from a service or script | Public HTTP API or SDK |
| Script terminal operations | CLI |
| Expose tools to an MCP-compatible agent | CLI MCP entry with appropriate authentication |
| Give a local agent DraPub usage instructions | Skillpack |
| Execute tasks on your device | Registered remote node or desktop execution |
API keys, sessions and task tokens have different scopes. Use your own account permissions and an explicit workspace. Internal task endpoints are not general-purpose interfaces for arbitrary clients.
Check connectivity and workspace before reading a small amount of data. Inspect permissions, costs and idempotency requirements before writes, generation or delivery. Handle CLI exit codes and API errors; request acceptance is not business completion.
See API, SDK, CLI and MCP and Runtime modes. Follow release instructions for package availability; a repository package name does not prove it is published to a public registry.
Q: Do I need to self-host just to access DraPub from a script?
**A: ** Start with the public HTTP API, SDK, or CLI, configure valid credentials and a workspace, and run a read-only check. Self-hosting has separate deployment and operational requirements.
Q: Does the SDK package name mean it is available from a public registry?
**A: ** Use the official release instructions for public installation. These examples apply to the repository workspace or an environment where the package has already been provided.