API access for agent configuration management

Feature Requests
,
1

API access for agent configuration management?

Hi everyone,

I’m working with multiple Pickaxe agents and wondering if there’s any way to programmatically manage agent configurations beyond what’s currently available in the Studio API.

Specifically looking for:

  1. System (and reminder) prompts - Can these be updated via API?
  2. Knowledge base files - Any way to manage/update these programmatically beyond document upload?
  3. Model selection - API access to change which model an agent uses?
  4. Agent tools/actions - Programmatic way to enable/disable capabilities?

Currently managing everything through the Studio UI, but would love to automate configuration updates across multiple agents if possible.

Is this on the roadmap, or are there any workarounds the community has found?

Thanks!

2

Hey @fvlr

Great ideas. It will be nice if we can get more granular control over studios via API.

Here’s a quick breakdown based on current Studio API capabilities:

Q1: System (and reminder) prompts - Can these be updated via API?

A1: Not at the moment. This is an excellent feature request for more granular control, and we’ll pass it along to the Pickaxe team.

Q2: Knowledge base files - Any way to manage/update these programmatically beyond document upload?

A2: Yes, the Studio API allows you to programmatically manage documents. You can create new documents, connect/detach them from agents, and list or retrieve specific documents by ID.

Q3: Model selection - API access to change which model an agent uses?

A3: This is also not currently available via the API, but it’s another valuable suggestion for future development.

Q4: Agent tools/actions - Programmatic way to enable/disable capabilities?

A4: This is a great point. Could you elaborate on what an ideal workflow would look like for you? For example, are you hoping to enable/disable existing Connected Actions or automate adding new Community Actions?

@nathanielmhld

1 Like
3

Thanks @Ned.Malki for the detailed breakdown! Really helpful to know what’s currently possible.

The knowledge base API is amazing - I used it yesterday, and it worked like a charm.

Regarding Q4 (tools/actions workflow), here’s what I’m thinking:

Ideal workflow would be:

  • Bulk configuration updates: When I need to update settings across multiple related agents, doing it programmatically rather than clicking through each one in the Studio UI

  • Version control: Being able to track and rollback configuration changes, especially for system prompts

  • Environment management: Having “staging” vs “production” configurations that I can switch between

  • Automated testing: After updating an agent’s configuration, being able to run automated tests to verify it’s working as expected

For tools/actions specifically:

  • Enable/disable existing Connected Actions based on different use cases or deployment stages

  • Batch operations (like “enable tool X on agents 1, 3, 5 but not 2, 4”)

  • Template management (apply the same set of tools to newly created agents)

The main pain point right now is that managing even 5-6 agents through the UI gets pretty time-consuming when you need to make coordinated updates.

Thanks again for the insights and for passing along the feature requests!