@devries-cameron20 / composio Mirror · read-only / commits / 7a14fabc8
Fork 0

Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

Mirrored from https://github.com/Camo67/composio.git

Synced Nov 22, 13:15 UTC

docs: replace 'integration' with 'toolkits' in docs copy (#2484)

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

Rahul Tarak committed Jan 28, 2026 at 00:19 UTC 7a14fabc8df7bc5ee876e3e08a545b4fb2bac888
5 files changed +10 -10
docs/content/docs/index.mdx
+1 -1
@@ -29,7 +29,7 @@ Composio powers 800+ toolkits, tool search, context management, authentication,
29 icon={<Wrench />}
30 title="Toolkits"
31 href="/toolkits"
32 - description="Browse 800+ integrations"
32 + description="Browse 800+ toolkits"
33 />
34 </Cards>
35
docs/content/docs/providers/custom-providers/python.mdx
+2 -2
@@ -3,14 +3,14 @@ title: Python Custom Provider
3 description: Learn how to create custom providers for any AI framework in Python
4 ---
5
6 -This guide shows how to create custom providers for the Composio Python SDK. Custom providers enable integration with different AI frameworks and platforms.
6 +This guide shows how to create custom providers for the Composio Python SDK. Custom providers enable compatibility with different AI frameworks and platforms.
7
8 ## Provider architecture
9
10 The Composio SDK uses a provider architecture to adapt tools for different AI frameworks. The provider handles:
11
12 1. **Tool format transformation**: Converting Composio tools into formats compatible with specific AI platforms
13 -2. **Platform-specific integration**: Providing helper methods for seamless integration
13 +2. **Platform-specific compatibility**: Providing helper methods for seamless compatibility
14
15 ## Types of providers
16
docs/content/docs/providers/custom-providers/typescript.mdx
+2 -2
@@ -3,7 +3,7 @@ title: TypeScript Custom Provider
3 description: Learn how to create custom providers for any AI platform in TypeScript
4 ---
5
6 -This guide provides a comprehensive walkthrough of creating custom providers for the Composio TypeScript SDK, enabling integration with different AI frameworks and platforms.
6 +This guide provides a comprehensive walkthrough of creating custom providers for the Composio TypeScript SDK, enabling compatibility with different AI frameworks and platforms.
7
8 ## Provider Architecture
9
@@ -11,7 +11,7 @@ The Composio SDK uses a provider architecture to adapt tools for different AI fr
11
12 1. **Tool Format Transformation**: Converting Composio tools into formats compatible with specific AI platforms
13 2. **Tool Execution**: Managing the flow of tool execution and results
14 -3. **Platform-Specific Integration**: Providing helper methods for seamless integration
14 +3. **Platform-Specific Compatibility**: Providing helper methods for seamless compatibility
15
16 ## Types of Providers
17
docs/content/docs/providers/openai.mdx
+2 -2
@@ -30,7 +30,7 @@ Read more about it in the [OpenAI documentation](https://platform.openai.com/doc
30
31 <Callout>
32 Before executing any tools that require authentication (like Gmail), you'll need to:
33 -1. [Create an Auth Configuration](/docs/authenticating-tools#creating-an-auth-config) for your integration
33 +1. [Create an Auth Configuration](/docs/authenticating-tools#creating-an-auth-config) for your app
34 2. [Set up a Connected Account](/docs/authenticating-tools#connecting-an-account) for the user.
35 </Callout>
36
@@ -118,7 +118,7 @@ The OpenAI Chat Provider is the default provider used by Composio SDK, but you c
118
119 <Callout>
120 Before executing any tools that require authentication (like Gmail), you'll need to:
121 -1. [Create an Auth Configuration](/docs/authenticating-tools#creating-an-auth-config) for your integration
121 +1. [Create an Auth Configuration](/docs/authenticating-tools#creating-an-auth-config) for your app
122 2. [Set up a Connected Account](/docs/authenticating-tools#connecting-an-account) for the user.
123 </Callout>
124
docs/content/docs/tools-direct/authenticating-tools.mdx
+3 -3
@@ -33,7 +33,7 @@ Each toolkit supports different authentication methods such as **OAuth**, **API
33 ### Configure scopes
34
35 Depending on your authentication method, you may need to configure scopes:
36 -- **OAuth2**: Configure scopes for what data and actions your integration can access.
36 +- **OAuth2**: Configure scopes for what data and actions your app can access.
37 - **API Key/Bearer Token**: Permissions are typically fixed based on the key's access level.
38 </Step>
39
@@ -86,7 +86,7 @@ You should create multiple auth configs for the same toolkit when you need:
86
87 With an auth config created, you're ready to authenticate your users!
88
89 -You can either use [**Connect Link**](#hosted-authentication-connect-link) for a hosted authentication flow, or use [**Direct SDK Integration**](#direct-sdk-integration).
89 +You can either use [**Connect Link**](#hosted-authentication-connect-link) for a hosted authentication flow, or use [**Direct SDK Setup**](#direct-sdk-setup).
90
91 <Callout>
92 User authentication requires a User ID - a unique identifier that groups connected accounts together. Learn more about [User Management](/docs/user-management) to understand how to structure User IDs for your application.
@@ -162,7 +162,7 @@ These settings will apply to all authentication flows using Connect Link, provid
162 For complete white-labeling including OAuth consent screens (removing Composio's domain), see [Custom Auth Configs - White-labeling](/docs/custom-auth-configs#white-labeling-the-oauth-consent-screen).
163 </Callout>
164
165 -### Direct SDK Integration
165 +### Direct SDK Setup
166
167 **Choose the section below that matches your toolkit's authentication method:**
168