From c6914bfd30239c675cbe0f1354294d59e75f865a Mon Sep 17 00:00:00 2001 From: Jakub Vul Date: Tue, 26 Aug 2025 09:19:57 -0400 Subject: [PATCH 1/5] Replace 'integration' with 'toolkit' terminology across documentation - Update references from 'integration' to 'toolkit' in meta files and components - Standardize terminology to use 'toolkit' consistently throughout the docs --- pages/home/_meta.tsx | 2 +- pages/home/google-adk/overview.mdx | 2 +- .../mcp-desktop-clients/claude-desktop-client.mdx | 2 +- pages/home/oai-agents/overview.mdx | 2 +- src/components/LandingPage.tsx | 13 ++++++------- src/components/custom/Toolkits/Toolkits.tsx | 10 +++++----- 6 files changed, 15 insertions(+), 16 deletions(-) diff --git a/pages/home/_meta.tsx b/pages/home/_meta.tsx index 9851a391..be102e59 100644 --- a/pages/home/_meta.tsx +++ b/pages/home/_meta.tsx @@ -19,7 +19,7 @@ export default { title: ( - Integrations + Toolkits ), href: "/toolkits", diff --git a/pages/home/google-adk/overview.mdx b/pages/home/google-adk/overview.mdx index 7d4275af..29ca8d4d 100644 --- 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 index 295cbcf2..1ed698aa 100644 --- 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 ``` -See [Arcade's Integrations](/toolkits) for more toolkits that can be installed. +See more of Arcade's [Toolkits](/toolkits) that can be installed. ### Set up Claude Desktop diff --git a/pages/home/oai-agents/overview.mdx b/pages/home/oai-agents/overview.mdx index 8c81a54a..19dfdf34 100644 --- a/pages/home/oai-agents/overview.mdx +++ b/pages/home/oai-agents/overview.mdx @@ -172,7 +172,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/src/components/LandingPage.tsx b/src/components/LandingPage.tsx index b4dd7ebf..13504583 100644 --- a/src/components/LandingPage.tsx +++ b/src/components/LandingPage.tsx @@ -62,11 +62,10 @@ export function LandingPage() { >

Arcade enables your AI agent to securely take real-world actions - through user-specific permissions, pre-built integrations with - Gmail, Slack, GitHub, and more. You can also build your own - agentic tools and MCP servers with our authoring and testing - suite. Arcade is your tool{" "} - engine,{" "} + through user-specific permissions, pre-built toolkits for Gmail, + Slack, GitHub, and more. You can also build your own agentic tools + and MCP servers with our authoring and testing suite. Arcade is + your tool engine,{" "} registry, and{" "} runtime.

@@ -319,8 +318,8 @@ export function LandingPage() { />

- Integrations + Toolkits

- There are 4 designations for Arcade integrations: + There are 4 designations for Arcade toolkits:

{Object.entries(typeConfig).map( @@ -118,11 +118,11 @@ export default function Toolkits({ tools, categories }: ToolkitsProps) {

{key === "arcade" && - "Official integrations developed and maintained by Arcade."} + "Official toolkits developed and maintained by Arcade."} {key === "verified" && - "Community-created integrations, thoroughly tested and verified by Arcade."} + "Community-created toolkits, thoroughly tested and verified by Arcade."} {key === "community" && - "Created and maintained by the Arcade community, offering a wide range of integrations."} + "Created and maintained by the Arcade community, offering a wide range of toolkits."} {key === "auth" && "Auth integrations allow you to develop custom tools that connect your agent APIs and services."}

From 448ddb1eb13de56005068c9b5300a8ccdbfd9ace Mon Sep 17 00:00:00 2001 From: Jakub Vul Date: Sun, 14 Sep 2025 13:50:49 -0400 Subject: [PATCH 2/5] Auth Integration -> Auth Provider --- src/components/custom/Toolkits/ToolCard.tsx | 2 +- src/components/custom/Toolkits/Toolkits.tsx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/components/custom/Toolkits/ToolCard.tsx b/src/components/custom/Toolkits/ToolCard.tsx index 60f64a0b..0a41f9b6 100644 --- a/src/components/custom/Toolkits/ToolCard.tsx +++ b/src/components/custom/Toolkits/ToolCard.tsx @@ -51,7 +51,7 @@ const typeConfig: Record< auth: { className: "border-purple-600/20 hover:border-primary bg-purple-600/[0.02] hover:bg-purple-600/[0.03]", - label: "Auth Integration", + label: "Auth Provider", icon: Key, color: "text-purple-400", }, diff --git a/src/components/custom/Toolkits/Toolkits.tsx b/src/components/custom/Toolkits/Toolkits.tsx index f8b45c32..ad2f47d1 100644 --- a/src/components/custom/Toolkits/Toolkits.tsx +++ b/src/components/custom/Toolkits/Toolkits.tsx @@ -36,7 +36,7 @@ const typeConfig = { color: "text-orange-400", }, auth: { - label: "Auth Integration", + label: "Auth Provider", icon: Key, color: "text-purple-400", }, From c4d1b12a82a3be77fc8ae8a06817b205f39c46e7 Mon Sep 17 00:00:00 2001 From: Jakub Vul Date: Sun, 14 Sep 2025 14:35:45 -0400 Subject: [PATCH 3/5] Update terminology: change 'the hosted Arcade Engine' to 'the Arcade Cloud Platform' --- pages/toolkits/development/github/github.mdx | 2 +- pages/toolkits/productivity/asana.mdx | 2 +- pages/toolkits/productivity/confluence.mdx | 2 +- pages/toolkits/productivity/dropbox/dropbox.mdx | 2 +- pages/toolkits/productivity/gmail.mdx | 2 +- pages/toolkits/productivity/google_calendar.mdx | 2 +- pages/toolkits/productivity/google_contacts.mdx | 2 +- pages/toolkits/productivity/google_docs.mdx | 2 +- pages/toolkits/productivity/notion.mdx | 2 +- pages/toolkits/productivity/outlook_calendar.mdx | 2 +- pages/toolkits/productivity/outlook_mail.mdx | 2 +- pages/toolkits/social-communication/linkedin.mdx | 2 +- pages/toolkits/social-communication/reddit.mdx | 2 +- pages/toolkits/social-communication/zoom.mdx | 2 +- 14 files changed, 14 insertions(+), 14 deletions(-) diff --git a/pages/toolkits/development/github/github.mdx b/pages/toolkits/development/github/github.mdx index 57aaacfa..fbf908ba 100644 --- a/pages/toolkits/development/github/github.mdx +++ b/pages/toolkits/development/github/github.mdx @@ -550,7 +550,7 @@ List review comments in a GitHub repository. The Arcade GitHub toolkit uses the [GitHub auth provider](/home/auth-providers/github) to connect to users' GitHub accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the GitHub auth provider](/home/auth-providers/github#configuring-github-auth) with your own GitHub app credentials. diff --git a/pages/toolkits/productivity/asana.mdx b/pages/toolkits/productivity/asana.mdx index cb7a7dfa..75f28d07 100644 --- a/pages/toolkits/productivity/asana.mdx +++ b/pages/toolkits/productivity/asana.mdx @@ -547,7 +547,7 @@ List the user workspaces. The Arcade Asana toolkit uses the [Asana auth provider](/home/auth-providers/asana) to connect to users' Asana accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Asana auth provider](/home/auth-providers/asana#configuring-asana-auth) with your own Asana app credentials. diff --git a/pages/toolkits/productivity/confluence.mdx b/pages/toolkits/productivity/confluence.mdx index 7fbb09b1..a5ac47e8 100644 --- a/pages/toolkits/productivity/confluence.mdx +++ b/pages/toolkits/productivity/confluence.mdx @@ -397,7 +397,7 @@ smart links, etc. organized by parent-child relationships. The Arcade Notion toolkit uses the [Notion auth provider](/home/auth-providers/notion) to connect to users' Notion accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Notion auth provider](/home/auth-providers/notion#configuring-notion-auth) with your own Notion app credentials. diff --git a/pages/toolkits/productivity/dropbox/dropbox.mdx b/pages/toolkits/productivity/dropbox/dropbox.mdx index 78304096..4f030b4c 100644 --- a/pages/toolkits/productivity/dropbox/dropbox.mdx +++ b/pages/toolkits/productivity/dropbox/dropbox.mdx @@ -117,7 +117,7 @@ Note: to call this tool, you must provide either `file_path` or `file_id`. The Arcade Dropbox toolkit uses the [Dropbox auth provider](/home/auth-providers/dropbox) to connect to users' Dropbox accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Dropbox auth provider](/home/auth-providers/dropbox#configuring-dropbox-auth) with your own Dropbox app credentials. diff --git a/pages/toolkits/productivity/gmail.mdx b/pages/toolkits/productivity/gmail.mdx index 6bffcf41..614ba97d 100644 --- a/pages/toolkits/productivity/gmail.mdx +++ b/pages/toolkits/productivity/gmail.mdx @@ -411,7 +411,7 @@ This tool does not take any parameters. The Arcade Gmail toolkit uses the [Google auth provider](/home/auth-providers/google) to connect to users' Google accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Google auth provider](/home/auth-providers/google#configuring-google-auth) with your own Google app credentials. diff --git a/pages/toolkits/productivity/google_calendar.mdx b/pages/toolkits/productivity/google_calendar.mdx index 750bd8e3..85ae439c 100644 --- a/pages/toolkits/productivity/google_calendar.mdx +++ b/pages/toolkits/productivity/google_calendar.mdx @@ -248,7 +248,7 @@ This tool does not take any parameters. The Arcade Google Calendar toolkit uses the [Google auth provider](/home/auth-providers/google) to connect to users' Google accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Google auth provider](/home/auth-providers/google#configuring-google-auth) with your own Google app credentials. diff --git a/pages/toolkits/productivity/google_contacts.mdx b/pages/toolkits/productivity/google_contacts.mdx index 84e0f537..3c8073b2 100644 --- a/pages/toolkits/productivity/google_contacts.mdx +++ b/pages/toolkits/productivity/google_contacts.mdx @@ -151,7 +151,7 @@ This tool does not take any parameters. The Arcade Google Contacts toolkit uses the [Google auth provider](/home/auth-providers/google) to connect to users' Google accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Google auth provider](/home/auth-providers/google#configuring-google-auth) with your own Google app credentials. diff --git a/pages/toolkits/productivity/google_docs.mdx b/pages/toolkits/productivity/google_docs.mdx index 55e19ac6..858ef5fe 100644 --- a/pages/toolkits/productivity/google_docs.mdx +++ b/pages/toolkits/productivity/google_docs.mdx @@ -350,7 +350,7 @@ Comment on a specific document by its ID. The Arcade Docs toolkit uses the [Google auth provider](/home/auth-providers/google) to connect to users' Google accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Google auth provider](/home/auth-providers/google#configuring-google-auth) with your own Google app credentials. diff --git a/pages/toolkits/productivity/notion.mdx b/pages/toolkits/productivity/notion.mdx index bf09dd63..79934e84 100644 --- a/pages/toolkits/productivity/notion.mdx +++ b/pages/toolkits/productivity/notion.mdx @@ -267,7 +267,7 @@ This tool does not take any parameters. The Arcade Notion toolkit uses the [Notion auth provider](/home/auth-providers/notion) to connect to users' Notion accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Notion auth provider](/home/auth-providers/notion#configuring-notion-auth) with your own Notion app credentials. diff --git a/pages/toolkits/productivity/outlook_calendar.mdx b/pages/toolkits/productivity/outlook_calendar.mdx index a208e08a..0e7330e1 100644 --- a/pages/toolkits/productivity/outlook_calendar.mdx +++ b/pages/toolkits/productivity/outlook_calendar.mdx @@ -159,7 +159,7 @@ If the user has not set a timezone for their calendar, then the timezone will be The Arcade Outlook Calendar toolkit uses the [Microsoft auth provider](/home/auth-providers/microsoft) to connect to users' Microsoft accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Microsoft auth provider](/home/auth-providers/microsoft#configuring-microsoft-auth) with your own Microsoft app credentials. diff --git a/pages/toolkits/productivity/outlook_mail.mdx b/pages/toolkits/productivity/outlook_mail.mdx index 618c076b..b4c865a2 100644 --- a/pages/toolkits/productivity/outlook_mail.mdx +++ b/pages/toolkits/productivity/outlook_mail.mdx @@ -306,7 +306,7 @@ List emails in the user's mailbox across all folders filtering by a property. The Arcade Outlook Mail toolkit uses the [Microsoft auth provider](/home/auth-providers/microsoft) to connect to users' Microsoft accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Microsoft auth provider](/home/auth-providers/microsoft#configuring-microsoft-auth) with your own Microsoft app credentials. diff --git a/pages/toolkits/social-communication/linkedin.mdx b/pages/toolkits/social-communication/linkedin.mdx index f98b20c7..5f14d9b2 100644 --- a/pages/toolkits/social-communication/linkedin.mdx +++ b/pages/toolkits/social-communication/linkedin.mdx @@ -68,7 +68,7 @@ Share a new text post to LinkedIn. The Arcade LinkedIn toolkit uses the [LinkedIn auth provider](/home/auth-providers/linkedin) to connect to users' LinkedIn accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the LinkedIn auth provider](/home/auth-providers/linkedin#configuring-linkedin-auth) with your own LinkedIn app credentials. diff --git a/pages/toolkits/social-communication/reddit.mdx b/pages/toolkits/social-communication/reddit.mdx index 79fca6d4..72d00bdf 100644 --- a/pages/toolkits/social-communication/reddit.mdx +++ b/pages/toolkits/social-communication/reddit.mdx @@ -345,7 +345,7 @@ Get posts that were created by the authenticated user sorted by newest first The Arcade Reddit toolkit uses the [Reddit auth provider](/home/auth-providers/reddit) to connect to users' Reddit accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Reddit auth provider](/home/auth-providers/reddit#configuring-reddit-auth) with your own Reddit app credentials. diff --git a/pages/toolkits/social-communication/zoom.mdx b/pages/toolkits/social-communication/zoom.mdx index b6aeecb8..c5519702 100644 --- a/pages/toolkits/social-communication/zoom.mdx +++ b/pages/toolkits/social-communication/zoom.mdx @@ -64,7 +64,7 @@ Retrieve the invitation note for a specific Zoom meeting. The Arcade Zoom toolkit uses the [Zoom auth provider](/home/auth-providers/zoom) to connect to users' Zoom accounts. -With the hosted Arcade Engine, there's nothing to configure. Your users will see `Arcade ` as the name of the application that's requesting permission. +With the Arcade Cloud Platform, there's nothing to configure. Your users will see `Arcade ` as the name of the application that's requesting permission. With a self-hosted installation of Arcade, you need to [configure the Zoom auth provider](/home/auth-providers/zoom#configuring-zoom-auth) with your own Zoom app credentials. From 3af9b4ada2689ce0fcab6fc1a142a6f78a21e1dd Mon Sep 17 00:00:00 2001 From: Jakub Vul Date: Sun, 14 Sep 2025 15:29:19 -0400 Subject: [PATCH 4/5] Update 'Arcade Cloud' to 'Arcade Cloud Platform' --- pages/home/auth-providers/asana.mdx | 4 ++-- pages/home/auth-providers/atlassian.mdx | 2 +- pages/home/auth-providers/clickup.mdx | 2 +- pages/home/auth-providers/discord.mdx | 2 +- pages/home/auth-providers/dropbox.mdx | 2 +- pages/home/auth-providers/github.mdx | 2 +- pages/home/auth-providers/google.mdx | 2 +- pages/home/auth-providers/hubspot.mdx | 4 ++-- pages/home/auth-providers/index.mdx | 4 ++-- pages/home/auth-providers/linear.mdx | 2 +- pages/home/auth-providers/linkedin.mdx | 2 +- pages/home/auth-providers/microsoft.mdx | 2 +- pages/home/auth-providers/notion.mdx | 2 +- pages/home/auth-providers/oauth2.mdx | 2 +- pages/home/auth-providers/reddit.mdx | 2 +- pages/home/auth-providers/salesforce.mdx | 2 +- pages/home/auth-providers/slack.mdx | 2 +- pages/home/auth-providers/spotify.mdx | 2 +- pages/home/auth-providers/twitch.mdx | 2 +- pages/home/auth-providers/x.mdx | 2 +- pages/home/auth-providers/zoom.mdx | 2 +- pages/toolkits/sales/hubspot.mdx | 2 +- 22 files changed, 25 insertions(+), 25 deletions(-) diff --git a/pages/home/auth-providers/asana.mdx b/pages/home/auth-providers/asana.mdx index c9a972a0..f3ce9cc2 100644 --- 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 index 80c9b568..0a8186ec 100644 --- 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 index 62833d3e..93dd3956 100644 --- a/pages/home/auth-providers/clickup.mdx +++ b/pages/home/auth-providers/clickup.mdx @@ -19,7 +19,7 @@ This auth provider is used by: 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 index 4c910d39..3433640e 100644 --- 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 index 06e4a562..8b802e3e 100644 --- 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 index eb2c9230..4423440d 100644 --- 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 index 88730d0a..3e5cfdde 100644 --- 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 index 25d8bfaa..b8b4151a 100644 --- 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 index cf9b3374..78d0995d 100644 --- a/pages/home/auth-providers/index.mdx +++ b/pages/home/auth-providers/index.mdx @@ -9,7 +9,7 @@ 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: @@ -17,7 +17,7 @@ It can be useful to configure your own auth provider for the following reasons: - 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 index f8252ca8..fc14755c 100644 --- 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 index 403f6c50..992332d0 100644 --- 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 index d142bb5d..d5c5a35e 100644 --- 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 index 28b0c546..621587b5 100644 --- 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 index 50b53b03..4b7f92cf 100644 --- 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 - 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. 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 index 39f793f9..c537de97 100644 --- 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 index 89357273..93bd82a0 100644 --- 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 - 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. 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 index 5379ea6b..e621e632 100644 --- 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 index f577be96..6473ca25 100644 --- 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 index 7ab2dc24..8d0029c3 100644 --- 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 index 2fc1801e..501d9a90 100644 --- 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 index 54ff547c..775182bd 100644 --- 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/toolkits/sales/hubspot.mdx b/pages/toolkits/sales/hubspot.mdx index bcc64175..8accfb5c 100644 --- a/pages/toolkits/sales/hubspot.mdx +++ b/pages/toolkits/sales/hubspot.mdx @@ -119,7 +119,7 @@ The Arcade Hubspot toolkit uses the [Hubspot auth provider](/home/auth-providers ### Arcade Cloud -The Arcade Cloud offers a default Hubspot auth provider. If you use it, there's nothing to configure. Your users will see `Arcade` as the name of the application requesting permission. +The Arcade Cloud Platform offers a default Hubspot auth provider. If you use it, there's nothing to configure. Your users will see `Arcade` as the name of the application requesting permission. Alternatively, you can [configure a custom Hubspot auth provider](/home/auth-providers/hubspot#use-your-own-hubspot-app-credentials) with your own Hubspot app credentials. This way, your users will see your application's name requesting permission. From a24b9007748c00630c945eefa6cb8b11fc0a7c17 Mon Sep 17 00:00:00 2001 From: Jakub Vul Date: Sun, 14 Sep 2025 16:09:14 -0400 Subject: [PATCH 5/5] Authentication Provider -> Auth Provider --- pages/home/glossary.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/pages/home/glossary.mdx b/pages/home/glossary.mdx index 0f6a5ba0..01ecd636 100644 --- 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