- With an API key. The key acts on its own, not as a person. What it can do depends on its access scope and on the Spaces and Pods added to it. Admins create keys in Admin > Developers: see API keys.
- As a signed-in user, for example after
dust loginin the Dust CLI. The request can do what that person can do in Dust, based on their role and permissions.
API key scopes
Older keys can show the Read & write scope, which you can’t choose for new keys.
Calls that need the Admin scope
With another scope, these calls return403. Unless the details say otherwise, a signed-in user needs the Admin role.
Calls that write to a Space or a Pod
These calls need write access to the Space or the Pod. Add it under Spaces and Pods when you create the key.- Upsert or delete documents, tables, and table rows in a folder, for example Upsert a document in a data source, Upsert a table, or Upsert rows.
- Upload a file into a Pod, and list the files already in it.
Calls that need a signed-in user
API keys can’t make these calls, whatever their scope. They return400, 401, or 403.
- Get feedbacks for a conversation, Submit feedback, and Delete feedback.
- List agents with
view=listorview=favorites. - Update agent configuration with
userFavorite. - Create a new conversation or Create a message with
clientSideMCPServerIdsorselectedMCPServerViewIdsin the message context. - Register a client-side MCP server.