Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Tavily" |
| 4 | description: "Public support knowledge for Tavily." |
| 5 | category: "auth-config" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-06-24T00:00:00Z" |
| 8 | tags: |
| 9 | - "tavily" |
| 10 | --- |
| 11 | # Tavily |
| 12 | |
| 13 | |
| 14 | ## Use COMPOSIO_SEARCH_TAVILY for Tavily search |
| 15 | |
| 16 | Use the updated Tavily search tool slug `COMPOSIO_SEARCH_TAVILY` when invoking Tavily search through Composio. If an older Tavily search slug returns schema-related gateway errors, switch to this slug before deeper debugging. |
| 17 | |
| 18 | ## Initiate Tavily API-key connections in the legacy JS SDK with generic_api_key |
| 19 | |
| 20 | For Tavily API-key auth in the legacy JS SDK, list the Tavily integration with `toolset.integrations.list({ appName: "tavily" })`, then initiate the connected account with `appName: "tavily"`, `authMode: "API_KEY"`, the integration ID, and `authConfig: { generic_api_key: "<tavily-api-key>" }`. This was provided as a workaround for a JS SDK issue, so prefer the current SDK flow when available. |
| 21 | |
| 22 | ## Use composio_search for auth-free Exa/Tavily-style search |
| 23 | |
| 24 | For auth-free web search through Composio, use the `composio_search` toolkit, which provides Exa/Tavily and other search capabilities without separate authentication. Use the standalone Tavily toolkit when a workflow specifically needs Tavily as its own provider-backed integration. |