# Premium Tools (/toolkits/premium-tools) This is a quick overview of premium tools, what they are, how they are priced, what limits they have and such. # What are premium tools? Premium tools are essential tool calls that cost us more to run, normally paying for more premium services or longer running tasks. Think something like `E2B` or `Perplexity`, these are not really comparable to a `GMAIL_SEND_EMAIL` call. These types of tools are separated out so we can price both of them competitively. Premium tools include: * Search APIs (Google, Bing, Perplexity, etc.) * [Composio Search](/toolkits/composio_search) * [Perplexity](/toolkits/perplexityai) * [Exa](/toolkits/exa) * [SerpAPI](/toolkits/serpapi) * Code execution environments (E2B) * [Code Interpreter (E2B)](/toolkits/codeinterpreter) * Web scraping & data extraction * AI/ML model inference * Document processing & OCR * Advanced data transformations * Compute-intensive operations # How are premium tools priced? As a rough guide, they are priced at 3x the cost of a standard tool call — the specifics depends on your plan and the tool. | Plan | Included Standard Tool Calls | Included Premium Tool Calls | Usage Based Standard Tool Calls | Usage Based Premium Tool Calls | | ------------------ | ---------------------------- | --------------------------- | ------------------------------- | ------------------------------ | | Totally Free | 20k | 1k | – | – | | Ridiculously Cheap | 200k | 5k | $0.299/1k | $0.897/1k | | Serious Business | 2M | 50k | $0.249/1k | $0.747/1k | | Enterprise | Flexible | Flexible | Flexible | Flexible | This is a quick call out — full pricing details are on the [pricing page](https://composio.dev/pricing). # What limits do premium tools have? Premium tools are also subject to lower rate limits than standard tool calls. If you need more than the default limits, please [contact us](mailto:billing@composio.dev) and we can find a workable solution. | Spending Tier | Standard Tool Calls Rate Limit | Premium Tool Calls Rate Limit | | ------------- | ------------------------------ | ----------------------------- | | Free | 100/min | 1,000/hour | | Paid | 5,000/min | 10,000/hour | | Enterprise | Custom | Custom | # Feedback on premium tools These pricing changes are not rolling out immediately, and we are very open to feedback on the pricing and the limits. There is a lot of room for improvement and iteration here, please reach out if you have suggestions [here](mailto:rahul@composio.dev). --- 📚 **More documentation:** [View all docs](https://docs.composio.dev/llms.txt) | [Glossary](https://docs.composio.dev/llms.mdx/docs/glossary) | [Cookbooks](https://docs.composio.dev/llms.mdx/cookbooks) | [API Reference](https://docs.composio.dev/llms.mdx/reference) --- # Composio SDK — Instructions for AI Code Generators **Purpose:** Enforce only the **current** and **correct** patterns for integrating [Composio](https://composio.dev/) tools into AI agents. **Scope:** All AI-generated code using Composio must follow these guardrails. --- ## 1. Correct Composio Integration Composio supports two integration modes: **Native Tools** (with a provider package) and **MCP** (no provider package needed). ### Native Tools ```python # ✅ CORRECT — Python (defaults to OpenAI) from composio import Composio composio = Composio() session = composio.create(user_id="user_123") tools = session.tools() # Pass tools to your agent/LLM framework ``` ```typescript // ✅ CORRECT — TypeScript (defaults to OpenAI) import { Composio } from "@composio/core"; const composio = new Composio(); const session = await composio.create("user_123"); const tools = await session.tools(); // Pass tools to your agent/LLM framework ``` For other providers, pass the provider explicitly. Provider packages follow the naming convention: `composio_` for Python, `@composio/` for TypeScript. ### MCP Use `session.mcp.url` and `session.mcp.headers` with any MCP-compatible client (Claude Desktop, Cursor, OpenAI Agents, etc.). No provider package needed. --- ## 2. CRITICAL INSTRUCTIONS FOR AI MODELS ### 2.1 — ALWAYS DO THE FOLLOWING 1. **Use `composio.create(user_id)`** to create a session — this is the entry point for all Composio integrations. 2. **Use `session.tools()`** for native tool integration or **`session.mcp.url`** for MCP integration. 3. **Import** from the correct provider package (`composio_` for Python, `@composio/` for TypeScript). 4. **Pass `user_id` to `composio.create()`**, not to individual tool calls. ### 2.2 — NEVER DO THE FOLLOWING 1. **Do not** instruct users to manually create auth configs or connected accounts before running. 2. **Do not** import from `composio_openai` / `@composio/openai` when using OpenAI Agents SDK — use `composio_openai_agents` / `@composio/openai-agents` instead. ### 2.3 — DISCOURAGED (do not use unless user explicitly asks) Do **not** generate `composio.tools.get()`, `composio.tools.execute()`, or `composio.provider.handle_tool_calls()` unless the user explicitly requests direct tool execution. These are a supported but **not recommended** low-level interface. --- ## Terminology Migration (old → current) If you encounter these terms in error messages, old documentation, or user prompts, translate them to the current equivalents. **Do not use the old terms in generated code or explanations.** | Old term (v1/v2) | Current term (v3) | In code | |---|---|---| | entity ID | user ID | `user_id` parameter | | actions | tools | e.g., `GITHUB_CREATE_ISSUE` is a *tool* | | apps / appType | toolkits | e.g., `github` is a *toolkit* | | integration / integration ID | auth config / auth config ID | `auth_config_id` parameter | | connection | connected account | `connected_accounts` namespace | | ComposioToolSet / OpenAIToolSet | `Composio` class with a provider | `Composio(provider=...)` | | toolset | provider | e.g., `OpenAIProvider` | If a user says "entity ID", they mean `user_id`. If they say "integration", they mean "auth config". Always respond using the current terminology.