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 21, 03:37 UTC
| 1 | A toolkit is a collection of related tools for a single app, like `gmail`, `github`, or `slack`. Each toolkit groups the actions for that service, its authentication requirements, and the trigger types it exposes. |
| 2 | |
| 3 | Reach for these endpoints when you want to: |
| 4 | |
| 5 | - List the toolkits in the catalog, sorted by popularity, to browse what is available before configuring a session. |
| 6 | - Fetch a single toolkit by `slug` for its name, logo, categories, and metadata. |
| 7 | - Fetch several toolkits at once with the multi endpoint. |
| 8 | - List the available toolkit categories to filter the catalog by use case. |
| 9 | - Read the toolkits changelog to track when tools or schemas change. |
| 10 | |
| 11 | These endpoints authenticate with your project API key in the `x-api-key` header. |
| 12 | |
| 13 | <Callout type="info"> |
| 14 | Tools within a toolkit are versioned. When you execute a tool, resolve to a known version with `toolkit_versions=latest` or a pinned dated version. See the [toolkit versioning migration guide](/docs/migration-guide/toolkit-versioning). |
| 15 | </Callout> |
| 16 | |
| 17 | To browse toolkits visually, see the [toolkits catalog](/toolkits). For the concepts and SDK usage, see [Tools and toolkits](/docs/how-composio-works) and [Configuring sessions](/docs/configuring-sessions). |