Change an agent's skills
apply_agent_skillsTurn registry skills on or off for a deployed agent and optionally upgrade Starter to Pro as one billed change: get a price quote, then confirm with its idempotency key.
Instructions
Turn registry skills on or off for a deployed agent, and optionally move it from Starter to Pro, as one billed change. Skills set the agent's monthly price and monthly credits. On a team agent only a team admin or the person who deployed the agent can change its skills; other members are refused and nothing is charged. Steps: 1) call without confirm. The tool checks the names, adds the skills they depend on, and returns the current and new monthly price, an estimate of what is charged now and an idempotency_key. Nothing changes yet. 2) Show the price to the user. 3) After they approve, call again with confirm: true and that idempotency_key. The key is tied to the quoted prices: if the price changed since the quote, nothing is applied and a new quote with a new key comes back. Reusing the key after a timeout is safe, the change is applied once. Billing: on a prepaid plan the monthly difference for the days left in the period is taken from the wallet at once, or credited to it when the price drops, and that credit can be spent until the period ends; on a card plan it is added to the next invoice. A running agent restarts once to load the skills. Newly enabled skills may still need credentials (set_agent_credentials, connect_agent_oauth) and do not create scheduled tasks (manage_agent_custom_skill does). Find skill names with list_agent_skills and the agent's current skills with get_my_agent. The agents playbook (get_playbook) has the full setup walkthrough.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tier | No | Optional: also move from Starter to Pro in this billed change. To upgrade without a skill change, use manage_agent_billing (upgrade_to_pro). | |
| skills | Yes | Skills to change, as name: true to turn on or name: false to turn off, for example {"int-instagram-post": true}. Registry names only (list_agent_skills). Custom skills and scheduled tasks (cs-...) are managed with manage_agent_custom_skill; channels such as Telegram turn on through set_agent_credentials. | |
| confirm | No | false (default) only returns the quote. true applies the change and charges it; it needs the idempotency_key from the quote. | |
| agent_guid | Yes | The deployed agent's guid, from list_my_agents. | |
| idempotency_key | No | With confirm: true, the key from the quote the user approved. It ties the approval to the quoted prices, and repeating the call with it after a timeout never applies the change twice. Omit it to get a quote. | |
| add_dependencies | No | Also turn on the skills that the enabled skills depend on (default true). Without them the change is refused. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tier | Yes | ||
| error | No | ||
| status | Yes | ||
| billing | Yes | ||
| changes | Yes | ||
| pricing | No | ||
| restart | Yes | ||
| agentGuid | Yes | ||
| nextAction | No | ||
| agentStatus | Yes | ||
| priceChanged | No | ||
| enabledSkills | No | ||
| idempotencyKey | No | ||
| credentialsNeeded | Yes |