# Pro Tools (/toolkits/pro-tools)

Some tool calls cost more to run — search APIs, code sandboxes, ML inference. We call those pro tools and price them separately.

# What counts as a pro tool? [#what-counts-as-a-pro-tool]

- [Search APIs](/toolkits/composio_search): Composio Search, Perplexity, Exa, SerpAPI

- [Code execution](/toolkits/codeinterpreter): Sandboxed runtimes like E2B

" title="Web scraping & data extraction" description="Crawlers and structured extraction" />

" title="AI/ML inference" description="Hosted model calls and embeddings" />

" title="Document processing & OCR" description="PDF, image, and document parsing" />

" title="Compute-intensive operations" description="Long-running or heavy transforms" />

# Pricing [#pricing]

Pro tool calls are roughly 3x the cost of a standard tool call. Full pricing is on the [pricing page](https://composio.dev/pricing).

| Plan               | Included Standard Tool Calls | Included Pro Tool Calls | Usage Based Standard Tool Calls | Usage Based Pro 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                   |

# Rate limits [#rate-limits]

Pro tools have lower rate limits than standard tool calls. If you need more, [contact us](mailto:billing@composio.dev).

| Spending Tier | Standard Tool Calls Rate Limit | Pro Tool Calls Rate Limit |
| ------------- | ------------------------------ | ------------------------- |
| Free          | 100/min                        | 1,000/hour                |
| Paid          | 5,000/min                      | 10,000/hour               |
| Enterprise    | Custom                         | Custom                    |

---

📚 **More documentation:** [View all docs](https://docs.composio.dev/llms.txt) | [Glossary](https://docs.composio.dev/llms.mdx/reference/glossary) | [Examples](https://docs.composio.dev/llms.mdx/examples) | [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_<provider>` for Python, `@composio/<provider>` 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_<provider>` for Python, `@composio/<provider>` 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.