You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: tighten Pro Tools and BYOC glossary copy (#946)
- Expand "Standard and Pro Tool Executions" into Standard and Pro
sub-sections with allowance, overage, and reclassification language
- Add current Pro tools list (as of 04/24)
- Tighten BYOC copy: specify Pro tools, Standard-rate billing benefit,
and API key credential detail
Made-with: Cursor
Co-authored-by: Valerie Fanelle <valeriefanelle@Valeries-MacBook-Pro.attlocal.net>
Copy file name to clipboardExpand all lines: app/en/resources/glossary/page.mdx
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -172,17 +172,25 @@ A 'tool execution' is a single call to a tool to interact with a remote system o
172
172
173
173
_Learn more about [tool executions](/guides/tool-calling)._
174
174
175
-
### Standard and Pro Tool executions
175
+
### Standard and Pro Tool Executions
176
176
177
-
Arcade tools are divided into 2 categories: Standard and Pro. While all tools have some cost for Arcade to run, Pro tools are significantly more costly - either due to infrastructure costs, the complexity of the tool, or a cost imposed by the provider of the tool. Pro tools cost more to execute and have different limits.
177
+
Arcade tools are divided into 2 categories: Standard and Pro. While all tools have some cost for Arcade to run, Pro tools are significantly more costly — either due to infrastructure costs, the complexity of the tool, or a cost imposed by the provider of the tool. Pro tools cost more to execute and have different limits.
178
178
179
-
Learn more about tool pricing [here](https://www.arcade.dev/pricing).
179
+
#### Standard Tool Executions
180
+
181
+
Standard tools are the default tier and cover the majority of Arcade's catalog. Each invocation of a Standard tool counts as one Standard Tool Execution against your plan's monthly allowance, with any overage billed per execution at the rate listed on the [pricing page](https://www.arcade.dev/pricing). Provider and infrastructure costs for Standard tools are absorbed by Arcade as part of the platform fee.
182
+
183
+
#### Pro Tool Executions
184
+
185
+
Pro tools incur materially higher operational cost than Standard tools due to underlying infrastructure (e.g., compute-intensive sandboxes), provider-imposed fees (e.g., per-call API charges from data providers), or tool complexity. Each invocation of a Pro tool counts as one Pro Tool Execution against your plan's monthly Pro allowance, with any overage billed per execution at the Pro rate listed on the [pricing page](https://www.arcade.dev/pricing). Arcade may reclassify tools between Standard and Pro from time to time as the underlying cost structure of a tool changes; any such reclassification applies prospectively.
186
+
187
+
As of 04/24, Pro tools include: E2B, Firecrawl, Google Finance, Google Flights, Google Hotels, Google Jobs, Google Maps, Google News, Google Search, Google Shopping, Imgflip, Walmart, and YouTube.
180
188
181
189
### Bring Your Own Credentials (BYOC)
182
190
183
-
Bring Your Own Credentials (BYOC) is a feature that allows you to use your own credentials to certain pro tools. This changes the cost of the tool execution, as you will be charged directly by the provider of the tool, rather than relying on Arcade to pay the bill for you.
191
+
Bring Your Own Credentials (BYOC) is a feature that allows you to use your own credentials to access Pro tools. This changes the cost of the tool execution, as you will be charged directly by the provider of the tool, rather than relying on Arcade to pay the bill for you. In exchange, the tool execution will be billed at the Standard rate. As of 04/26/2026, most credentials required for Pro tools are API Keys specific to the service being accessed.
184
192
185
-
To set your own credentials, set the requisite secret within the Arcade Dashboard, overwriting the default 'static' credentials.
193
+
To set your own credentials, set the requisite secret(s) within the Arcade Dashboard Secrets page, overwriting the default 'static' credentials. You can also set the secrets using the Arcade CLI.
0 commit comments