Documentation
Integration plans
Future API and MCP integrations are intended to expose the same Dime creation and licensing lifecycle to other tools. No public endpoint is available today.
Product guides · Updated October 2026Connected records
Identity, project revision, owner decision, licence and release state should travel together. Access to an identity must never stand in for permission to generate a particular project.
Authorised access
Integrations need server authentication and permissions for each identity and project. Provider credentials belong on the server, away from public pages and browser storage.
Current availability
This website has no public Dime API, SDK or MCP endpoint. Its recording, download and template browser work locally in your browser; product interfaces are demonstrations.
Discuss an integration
Share the workflow you want to connect and how owner approvals and usage history should be maintained.
Contact the team