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 | import { TOOLKIT_COUNT_LABEL } from '@/lib/toolkit-count'; |
| 2 | import { PROVIDERS } from '@/lib/providers'; |
| 3 | |
| 4 | export const revalidate = false; |
| 5 | |
| 6 | /** Curated routing map; the exhaustive catalog lives at /llms-index.txt. */ |
| 7 | export function GET() { |
| 8 | // Keep the concise map focused; all adapters remain on the providers page. |
| 9 | const providerGuides = PROVIDERS['ai-sdks'] |
| 10 | .filter(provider => provider.name === 'OpenAI' || provider.name === 'Anthropic') |
| 11 | .map(provider => `- [${provider.name}](https://docs.composio.dev${provider.href}.md)`) |
| 12 | .join('\n'); |
| 13 | return new Response(`# Composio Documentation |
| 14 | |
| 15 | > Connect users to ${TOOLKIT_COUNT_LABEL} apps. Use Composio for auth with your own tools, or add tool discovery and execution to an agent. |
| 16 | |
| 17 | Use Composio Platform when users or tenants connect accounts to your application. Use Composio For You for personal automation with your own accounts. Use the current session SDK. REST v3.1 is current; REST v3.0 is legacy. |
| 18 | |
| 19 | ## Before you implement |
| 20 | |
| 21 | Inspect the project's framework, agent architecture, authentication, and user or tenant identity model. Explain where Composio fits. If the intended workflow is unclear, ask what the user wants their application or agent to accomplish with connected apps before making changes. |
| 22 | |
| 23 | Load and follow the official [Composio Agent Skill](https://github.com/ComposioHQ/composio/blob/next/skills/composio/SKILL.md) for setup guidance and implementation patterns. If it is missing, install it for the project with \`npx skills add ComposioHQ/composio --skill composio\`, requesting approval if your host requires it. If skills are unsupported or installation fails, use the documentation linked below and report that fallback. |
| 24 | |
| 25 | If unclear, distinguish application integration from connecting apps to the coding agent. Fetch Markdown below; use the complete index for other guides. |
| 26 | |
| 27 | ## Choose your path |
| 28 | |
| 29 | - [Platform or For You](https://docs.composio.dev/docs.md): Choose between building an application and using your own connected apps. |
| 30 | - [Set up a coding agent](https://docs.composio.dev/docs/agent-setup.md): Install the Composio skill to add Composio to an existing project. |
| 31 | - [Auth for your own tools](https://docs.composio.dev/docs/authentication/managed-auth-for-custom-tools.md): Per-user OAuth with Connect Link + Proxy Execute. Keep your backend or MCP tools; receive responses, not tokens. |
| 32 | - [SDK quickstart](https://docs.composio.dev/docs/quickstart.md): Install Python or TypeScript packages, create a session, and run an agent. |
| 33 | - [Authenticate an unattended agent](https://docs.composio.dev/docs/agent-setup/unattended-authentication.md): When no human is available, use \`composio login --agent\`, configure a project API key, and verify a live tool call. Human account access still requires authorization. |
| 34 | - [Native agent plugins](https://docs.composio.dev/docs/agent-plugins.md): Use your own apps from Codex or Claude Code. |
| 35 | - [Connect an MCP client](https://docs.composio.dev/docs/composio-connect.md): Connect an existing client to your apps over MCP. |
| 36 | |
| 37 | ## Build an application |
| 38 | |
| 39 | - [Core concepts](https://docs.composio.dev/docs/how-composio-works.md): Understand users, sessions, toolkits, and tool execution. |
| 40 | - [Authentication](https://docs.composio.dev/docs/authentication.md): Distinguish auth configs from connected accounts and connect your application's users. |
| 41 | - [B2B agents](https://docs.composio.dev/docs/b2b-agents.md): Tenant/member connection ownership and authorization. |
| 42 | - [Token custody](https://docs.composio.dev/docs/security/token-custody.md): Credential storage, redaction, VPC, self-hosting, and customer-managed keys. |
| 43 | - [Proxy Execute](https://docs.composio.dev/docs/extending-sessions/proxy-execute.md): Call provider endpoints that tools don't cover without retrieving the token. |
| 44 | - [Configure sessions](https://docs.composio.dev/docs/configuring-sessions.md): Select toolkits, auth configs, and connected accounts for a user. |
| 45 | - [SDKs and frameworks](https://docs.composio.dev/docs/providers.md): Choose a framework provider. |
| 46 | - [Sessions via MCP](https://docs.composio.dev/docs/sessions-via-mcp.md): Give an application-created session to an MCP-compatible framework. |
| 47 | - [Single-toolkit MCP](https://docs.composio.dev/docs/single-toolkit-mcp.md): Build an MCP server scoped to one toolkit. |
| 48 | - [Troubleshooting](https://docs.composio.dev/kb.md): Diagnose authentication, connection, and execution failures. |
| 49 | - [Production rate limits](https://docs.composio.dev/reference/rate-limits.md): Plan for request limits before deployment. |
| 50 | |
| 51 | ## Provider guides |
| 52 | |
| 53 | ${providerGuides} |
| 54 | |
| 55 | ## Session SDK reference |
| 56 | |
| 57 | - [TypeScript session creation and reuse](https://docs.composio.dev/reference/sdk-reference/typescript/sessions.md): Look up the exact \`sessions.create()\` and \`sessions.use()\` signatures. |
| 58 | - [TypeScript Session methods and results](https://docs.composio.dev/reference/sdk-reference/typescript/session.md): Look up \`tools()\`, \`search()\`, \`execute()\`, \`update()\`, and returned properties. |
| 59 | - [Python Session methods and results](https://docs.composio.dev/reference/sdk-reference/python/session.md): Look up Python argument names, return types, and examples. |
| 60 | - [Session configuration examples](https://docs.composio.dev/docs/configuring-sessions.md): Find language-specific create options and update behavior. |
| 61 | |
| 62 | Fetch these Markdown pages directly for exact call shapes; search-result summaries may omit code. Use the installed package's version-matched reference when it differs from the current website. |
| 63 | |
| 64 | ## API Reference (v3.1, current) |
| 65 | |
| 66 | - [Current REST API](https://docs.composio.dev/reference.md): Use the current base URL and browse endpoint groups. |
| 67 | |
| 68 | ## API Reference (v3.0, legacy) |
| 69 | |
| 70 | - [Legacy REST API](https://docs.composio.dev/reference/v3.md): Maintain existing v3.0 integrations. Use v3.1 for new code. |
| 71 | |
| 72 | ## Optional |
| 73 | |
| 74 | - [Changelog](https://docs.composio.dev/docs/changelog.md): Find dated release notes and read what changed. |
| 75 | |
| 76 | - [Complete documentation index](https://docs.composio.dev/llms-index.txt): All guides, SDK references, endpoint groups, and toolkit pages, with legacy routes labeled. |
| 77 | - [Knowledge Base](https://docs.composio.dev/kb.md): Find support answers and toolkit-specific troubleshooting. |
| 78 | - [Examples](https://docs.composio.dev/examples.md): Browse complete application examples. |
| 79 | - [Full documentation](https://docs.composio.dev/llms-full.txt): Load all current page bodies when individual pages are insufficient. |
| 80 | `, { headers: { 'Content-Type': 'text/plain; charset=utf-8' } }); |
| 81 | } |