Benji Weber

Posted in Feedback·

Benji Weber

Missing Required Limit Field in API Docs for Post Search

https://docs.dust.tt/reference/post_api-v1-w-wid-search docs page appears to be missing a required limit field.

0Comments

Posted in Feedback·

Benji Weber

Update on 'actions' Field in Agent API Response Status

The "actions" field on agent API response still seems to always be empty. A few months ago you indicated it was temporarily deactivated due to performance issues. Any indication when it'll be working? Any other ideas how we can introspect / query which tools are accessible to each agent? https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-agent-configurations-sid https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-agent-configurations The webapp appears to get this from https://dust.tt/api/w/$wId/builder/assistants/$sId/actions However, this does not seem to be exposed in the public API. I can't authenticate using an access token against this endpoint, The https://dust.tt/api/w/$wId/assistant/agent_configurations/$sId/export/yaml endpoint would also be an alternative, but also does not seem to be exposed in the public API.

0Comments

Commented on Querying Agent Tool Access via API: A Solution Nee...·Posted inHelp

Benji Weber

Any timeline for enumerating tools via the API?

Commented on Querying Agent Tool Access via API: A Solution Nee...·Posted inHelp

Benji Weber

Interestingly actions are listed for the built in agents on the response from https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-agent-configurations but not for our custom built agents

Commented on Potential Bugs with API Key and Agent Configuratio...·Posted inHelp

Benji Weber

Oh the https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-agent-configurations list api still works wich is a workaround for (2) for now

Posted in Help·

Benji Weber

Potential Bugs with API Key and Agent Configurations

A couple of potential bugs that seem to have appeared in the past week. Please let me know if I'm just doing it wrong.

1.
After creating an API key, it no longer seems to be copyable. The copy button copies the asterisks instead of the raw value. This was working last week.
2.
The list agents ( [search by name](https://docs.dust.tt/reference/get_api-v1-w-wid-assistant-agent-configurations-search) ) API is no longer returning our agent configurations. This was working last week searching by a wildcard (%). Now I can't even search by an agent by exact name, I've tried various variations and nothing is returning any matches.

2Comments

Commented on Querying Agent Tool Access via API: A Solution Nee...·Posted inHelp

Benji Weber

Thanks for confirming. This would indeed be useful. One of our usecases is for central governance. A separate API call would be fine if it's computationally expensive.

Commented on Querying Agent Tool Access via API: A Solution Nee...·Posted inHelp

Benji Weber

Actions comes back as an empty array for me. Does it only list custom apps? I was expecting the web browser tool to show up there

Commented on Querying Agent Tool Access via API: A Solution Nee...·Posted inHelp

Benji Weber

Thanks. I'm not trying to query the tools. I'm looking to introspect what tools it has available. It seems I can enumerate everything else like it's instructions, data sources, apps, but not its tools

Posted in Help·

Benji Weber

Querying Agent Tool Access via API: A Solution Needed

Is there a way to query the tools an agent has access to via the API? The agent configuration API response doesn't seem to list the tools, just the instructions.

9Comments