Limits and cost
This guide explains the limits and cost structure of using Custom Actions with your AI agent.
What is a custom action?
A Custom Action connects your agent to an external system through an MCP (Model Context Protocol) server. This enables the agent to:
- Fetch live information (e.g., check order status).
- Trigger actions (e.g., create a support ticket).
- Integrate with third-party apps and workflows.
👉 Learn more about Custom Actions
Limits
- Maximum number of actions per agent
You can add up to three Custom Actions to a single agent. This allows flexibility to connect your agent with different external systems (e.g., CRM, ERP, or ticketing system).
- Only one action active at a time
Even if you’ve added multiple Custom Actions, you can only activate one action at a time. This ensures that the agent doesn’t call conflicting systems during a single query.
- Number of action calls per query
Your agent can use up to three action calls in a single query.
Example: If a user asks for both order status, booking a call, and opening a support ticket, the agent can handle those requests in one conversation turn — but will stop after three.
- Fallback behavior
If the agent reaches its limit (three actions per query) or if an inactive action is requested, it will respond gracefully by explaining that the action cannot be performed.
Cost
Every Custom Action has a cost associated with its usage:
1. Per-action usage
Each action usage consumes 1 additional query.
Example: If the agent uses two Custom Actions in one query, that counts as two extra queries.
2. No unused overhead
If no Custom Actions are executed while generating the response, no additional cost is added. The query will be charged at the regular rate.
3. Comparison with normal queries
Standard chat messages = 1 query each
Custom Action-enabled queries = 1 query per message + 1 query per action used.
Example:
- User sends one message → agent replies without any actions → cost = 1 query.
- User sends one message → agent replies with two Custom Actions → cost = 3 queries (1 base + 2 actions).
Related articles
Updated about 7 hours ago