ArcadeAI · evantahler · Sep 15, 2025 · Aug 26, 2025 · Sep 14, 2025 · Sep 14, 2025
diff --git a/pages/home/_meta.tsx b/pages/home/_meta.tsx
@@ -19,7 +19,7 @@ export default {
     title: (
       <span className="flex items-center gap-2 font-medium">
         <Plug className="size-4" />
-        Integrations
+        Toolkits
       </span>
     ),
     href: "/toolkits",

diff --git a/pages/home/auth-providers/asana.mdx b/pages/home/auth-providers/asana.mdx
@@ -22,7 +22,7 @@ This auth provider is used by:
 
 ## Use Arcade's Default Asana Auth Provider
 
-Arcade offers a default Asana auth provider that you can use in the Arcade Cloud. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
+Arcade offers a default Asana auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
 
 If you choose to use Arcade's Asana auth, you don't need to configure anything. Follow the [Asana toolkit examples](/toolkits/productivity/asana) to get started calling Asana tools.
 
@@ -34,7 +34,7 @@ If you choose to use Arcade's Asana auth, you don't need to configure anything.
 
 In a production environment, you will most likely want to use your own Asana app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Asana credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Asana credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Asana app credentials, let's go through the steps to create an Asana app.
 

diff --git a/pages/home/auth-providers/atlassian.mdx b/pages/home/auth-providers/atlassian.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Atlassian app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Atlassian credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Atlassian credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Atlassian app credentials, let's go through the steps to create an Atlassian app.
 

diff --git a/pages/home/auth-providers/clickup.mdx b/pages/home/auth-providers/clickup.mdx
@@ -19,7 +19,7 @@ This auth provider is used by:
 </Note>
 In a production environment, you will most likely want to use your own ClickUp app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own ClickUp credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own ClickUp credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your ClickUp app credentials, let's go through the steps to create a ClickUp app.
 

diff --git a/pages/home/auth-providers/discord.mdx b/pages/home/auth-providers/discord.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Discord app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Discord credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Discord credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Discord app credentials, let's go through the steps to create a Discord app.
 

diff --git a/pages/home/auth-providers/dropbox.mdx b/pages/home/auth-providers/dropbox.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Dropbox app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Dropbox credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Dropbox credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Dropbox app credentials, let's go through the steps to create a Dropbox app.
 

diff --git a/pages/home/auth-providers/github.mdx b/pages/home/auth-providers/github.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own GitHub app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own GitHub credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own GitHub credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your GitHub app credentials, let's go through the steps to create a GitHub app.
 

diff --git a/pages/home/auth-providers/google.mdx b/pages/home/auth-providers/google.mdx
@@ -28,7 +28,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Google app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Google credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Google credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Google app credentials, let's go through the steps to create a Google app.
 

diff --git a/pages/home/auth-providers/hubspot.mdx b/pages/home/auth-providers/hubspot.mdx
@@ -21,7 +21,7 @@ This auth provider is used by:
 
 ## Use Arcade's Default Hubspot Auth Provider
 
-Arcade offers a default Hubspot auth provider that you can use in the Arcade Cloud. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
+Arcade offers a default Hubspot auth provider that you can use in the Arcade Cloud Platform. In this case, your users will see `Arcade` as the name of the application that's requesting permission.
 
 If you choose to use Arcade's Hubspot auth, you don't need to configure anything. Follow the [Hubspot toolkit examples](/toolkits/sales/hubspot) to get started calling Hubspot tools.
 
@@ -33,7 +33,7 @@ If you choose to use Arcade's Hubspot auth, you don't need to configure anything
 
 In a production environment, you will most likely want to use your own Hubspot app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Hubspot credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Hubspot credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Hubspot app credentials, let's go through the steps to create a Hubspot app.
 

diff --git a/pages/home/auth-providers/index.mdx b/pages/home/auth-providers/index.mdx
@@ -9,15 +9,15 @@ import { ToolCard } from "@/components/ToolCard";
 
 Auth providers enable users to seamlessly and securely allow Arcade tools to access their data.
 
-Arcade has several auth providers available in the Arcade cloud so you don't have to configure your own. However, using Arcade's auth providers means that your users will see the Arcade brand (name and logo) on the auth screen and your authentications will share any rate limits from those providers with other Arcade customers.
+Arcade has several auth providers available in the Arcade Cloud Platform so you don't have to configure your own. However, using Arcade's auth providers means that your users will see the Arcade brand (name and logo) on the auth screen and your authentications will share any rate limits from those providers with other Arcade customers.
 
 It can be useful to configure your own auth provider for the following reasons:
 
 - You want to use your own brand on the auth screen
 - You want to isolate your rate limits from other Arcade customers
 - You want to use a provider that Arcade [does not have a built-in integration for](/home/auth-providers/oauth2)
 
-After adding an auth provider used by an Arcade tool, executing the tool will automatically use your auth provider. Even in the Arcade Cloud, your auth provider will take precedence over the arcade-provided auth provider.
+After adding an auth provider used by an Arcade tool, executing the tool will automatically use your auth provider. Even in the Arcade Cloud Platform, your auth provider will take precedence over the arcade-provided auth provider.
 
 Adding multiple providers of the same type, not including the arcade-provided ones, can cause Arcade's tool authorization to fail, see [Using multiple providers of the same type](#using-multiple-providers-of-the-same-type) for more information.
 

diff --git a/pages/home/auth-providers/linear.mdx b/pages/home/auth-providers/linear.mdx
@@ -21,7 +21,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Linear app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Linear credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Linear credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Linear app credentials, let's go through the steps to create a Linear app.
 

diff --git a/pages/home/auth-providers/linkedin.mdx b/pages/home/auth-providers/linkedin.mdx
@@ -21,7 +21,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own LinkedIn app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own LinkedIn credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own LinkedIn credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your LinkedIn app credentials, let's go through the steps to create a LinkedIn app.
 

diff --git a/pages/home/auth-providers/microsoft.mdx b/pages/home/auth-providers/microsoft.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Microsoft app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Microsoft credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Microsoft credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Microsoft app credentials, let's go through the steps to create a Microsoft app.
 

diff --git a/pages/home/auth-providers/notion.mdx b/pages/home/auth-providers/notion.mdx
@@ -21,7 +21,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Notion app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Notion credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Notion credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Notion app credentials, let's go through the steps to create a Notion app.
 

diff --git a/pages/home/auth-providers/oauth2.mdx b/pages/home/auth-providers/oauth2.mdx
@@ -37,7 +37,7 @@ When configuring your app in the OAuth 2.0 enabled service, you must use `https:
 ### Using the Arcade Dashboard
 
 <Tip>
-  When using the Arcade Cloud, the Dashboard is available at [`https://api.arcade.dev/dashboard`](https://api.arcade.dev/dashboard). If you are [self-hosting Arcade](/home/local-deployment/install/overview), by default the Dashboard is available at [`http://localhost:9099/dashboard`](http://localhost:9099/dashboard). Adjust the host and port, if necessary, to match your environment.
+  When using the Arcade Cloud Platform, the Dashboard is available at [`https://api.arcade.dev/dashboard`](https://api.arcade.dev/dashboard). If you are [self-hosting Arcade](/home/local-deployment/install/overview), by default the Dashboard is available at [`http://localhost:9099/dashboard`](http://localhost:9099/dashboard). Adjust the host and port, if necessary, to match your environment.
 </Tip>
 
 1. Navigate to the OAuth section of the Arcade Dashboard and click **Add OAuth Provider**.

diff --git a/pages/home/auth-providers/reddit.mdx b/pages/home/auth-providers/reddit.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Reddit app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Reddit credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Reddit credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Reddit app credentials, let's go through the steps to create a Reddit app.
 

diff --git a/pages/home/auth-providers/salesforce.mdx b/pages/home/auth-providers/salesforce.mdx
@@ -4,7 +4,7 @@ import { SignupLink } from "@/components/Analytics";
 # Salesforce Auth Provider
 
 <Note>
-  At this time, Arcade does not offer a default Salesforce Auth Provider and cannot support Salesforce auth in the Arcade Cloud. To use Salesforce auth, the [Salesforce toolkit](/toolkits/sales/salesforce), or to develop your [custom Salesforce tools](/home/build-tools/create-a-toolkit), you must [self-host the Arcade Engine](/home/local-deployment/install/local) and create a custom Auth Provider with your own Salesforce OAuth 2.0 credentials as described below.
+  At this time, Arcade does not offer a default Salesforce Auth Provider and cannot support Salesforce auth in the Arcade Cloud Platform. To use Salesforce auth, the [Salesforce toolkit](/toolkits/sales/salesforce), or to develop your [custom Salesforce tools](/home/build-tools/create-a-toolkit), you must [self-host the Arcade Engine](/home/local-deployment/install/local) and create a custom Auth Provider with your own Salesforce OAuth 2.0 credentials as described below.
 </Note>
 
 The Salesforce auth provider enables tools and agents to call Salesforce APIs on behalf of a user. Behind the scenes, the Arcade Engine and the Salesforce auth provider seamlessly manage Salesforce OAuth 2.0 authorization for your users.

diff --git a/pages/home/auth-providers/slack.mdx b/pages/home/auth-providers/slack.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Slack app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Slack credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Slack credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Slack app credentials, let's go through the steps to create a Slack app.
 

diff --git a/pages/home/auth-providers/spotify.mdx b/pages/home/auth-providers/spotify.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Spotify app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Spotify credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Spotify credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Spotify app credentials, let's go through the steps to create a Spotify app.
 

diff --git a/pages/home/auth-providers/twitch.mdx b/pages/home/auth-providers/twitch.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Twitch app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Twitch credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Twitch credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Twitch app credentials, let's go through the steps to create a Twitch app.
 

diff --git a/pages/home/auth-providers/x.mdx b/pages/home/auth-providers/x.mdx
@@ -28,7 +28,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own X app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own X credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own X credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your X app credentials, let's go through the steps to create a X app.
 

diff --git a/pages/home/auth-providers/zoom.mdx b/pages/home/auth-providers/zoom.mdx
@@ -27,7 +27,7 @@ This auth provider is used by:
 
 In a production environment, you will most likely want to use your own Zoom app credentials. This way, your users will see your application's name requesting permission.
 
-You can use your own Zoom credentials in both the Arcade Cloud and in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
+You can use your own Zoom credentials in both the Arcade Cloud Platform or in a [self-hosted Arcade Engine](/home/local-deployment/install/local) instance.
 
 Before showing how to configure your Zoom app credentials, let's go through the steps to create a Zoom app.
 

diff --git a/pages/home/glossary.mdx b/pages/home/glossary.mdx
@@ -91,11 +91,11 @@ Monthly Active Users are the unique end-users (counted by `user_id`) who have ex
 
 User Challenges are the count of authorizations performed for any user (specified by `user_id` in Arcade's SDKs and APIs). Authorization challenges occur when a user needs a new permission or scope that they don't currently have, including previously-held scopes that were deleted or expired. The same user authenticating to multiple toolkits will have a User Challenge for each toolkit  (e.g. once for Slack and once for Google). We also count the act of elevating permissions to a user who has already authenticated to a toolkit (e.g. adding a "write" scope when they previously only had a "read" scope).
 
-### Authentication Provider
+### Auth Provider
 
-An 'authentication provider' is a service that your users can authenticate to grant the agent access to their data or to take actions on their behalf.  This can be a hosted service provider like Google or Slack, or it can be a custom OAuth provider.  Multiple Toolkits may share the same authentication provider (e.g. Gmail and Google Drive share the same Google OAuth authentication provider).  Custom authentication providers are defined in the Arcade Dashboard or your Engine YAML if self-hosting.
+An 'auth provider' is a service that your users sign in with to let the agent access their data or take actions on their behalf. This can be a hosted service like Google or Slack, or a custom OAuth provider. Multiple Toolkits may share the same auth provider (for example, Gmail and Google Drive both use Google's OAuth provider). Custom auth providers are defined in the Arcade Dashboard, or in your Engine YAML if you're self-hosting.
 
-*Learn more about [authentication providers](/home/auth-providers).*
+*Learn more about [auth providers](/home/auth-providers).*
 
 ### Authorization Scope
 

diff --git a/pages/home/google-adk/overview.mdx b/pages/home/google-adk/overview.mdx
@@ -134,7 +134,7 @@ Arcade provides a variety of toolkits you can use with your agents:
 - **Web**: Web search, content extraction
 - **And more**: Weather, financial data, etc.
 
-For a full list of available toolkits, visit the [Arcade Integrations](/toolkits) documentation.
+For a full list of available toolkits, visit the [Arcade Toolkits](/toolkits) documentation.
 
 ## Next steps
 

diff --git a/pages/home/mcp-desktop-clients/claude-desktop-client.mdx b/pages/home/mcp-desktop-clients/claude-desktop-client.mdx
@@ -20,7 +20,7 @@ pip install arcade-ai
 pip install arcade-google
 ```
 <Tip>
-See [Arcade's Integrations](/toolkits) for more toolkits that can be installed.
+See more of Arcade's [Toolkits](/toolkits) that can be installed.
 </Tip>
 
 ### Set up Claude Desktop