Dust API: connect your Dust workspace
Idun Cockpit reads your Dust workspace’s usage with a workspace API key, which an administrator creates in Dust. From it, the Cockpit draws the conversations, the agents and the credit cost of each message. To see which shared agents run and which sleep, see our article on Dust.
What you need
Section titled “What you need”- An administrator of the Dust workspace.
- Your workspace’s address:
app.dust.ttor, for the European region,eu.dust.tt.
The steps
Section titled “The steps”-
Create an API key
In the workspace administration, the administrator creates an API key (it starts with
sk-). Give it the administrator role, for the analytics export and for reading conversations. -
Send it to us
Send the key, the address and the workspace ID through the channel agreed at the start of the audit, never by email.
-
Choose the period
Tell us the period to measure. The Cockpit reads the workspace analytics, then each conversation they point to.
What is measured, and what is not
Section titled “What is measured, and what is not”- Measured: conversations and the agents that answer them, each agent’s definition, the tools called, and the credit cost of each message.
- Not available: tokens; Dust bills in credits and does not provide them.
Frequently asked questions
Section titled “Frequently asked questions”Are private conversations read?
Section titled “Are private conversations read?”No, if the “private conversations by default” setting is on: an API key cannot read a conversation restricted to its participants. The Cockpit counts these conversations as missed, and says so.
Why the key, and not the dashboard analytics?
Section titled “Why the key, and not the dashboard analytics?”Dust’s analytics count messages, active people and credits, without the content. The Cockpit needs the conversations to detect use cases.
To see what the tool shows on your own tools, book a call.