Structured programmatic access
Read processes, update metadata and graph state, import/export canonical JSON, and participate in review and governance workflows.
Oroko Developer Platform
Build with process context, not screenshots.
Use Oroko's REST API to work with processes programmatically, or connect the public MCP server so compatible AI clients can read and act on governed process data using the same permissions as the connected user.
Two ways to integrate
One permission model.
Developer keys act as their owning Oroko user. API and MCP access never bypass workspace membership, process access, governance, revision checks or approved-process locking.
AI-native process access
Expose Oroko tools to MCP-compatible clients. Read tools are direct; write tools require explicit confirmation and remain subject to Oroko permissions.
One developer key
Create a developer key inside Oroko and use the same X-Oroko-Key credential with both REST API and MCP.
Start here
Create a developer key in Oroko
Open Developer → Keys in the Oroko app, generate a key, then verify it with GET /me. Keep the secret private: integrations stop immediately if the key is disabled or deleted.