---
canonical_url: "https://docs.composio.dev/docs/migration-guide/no-auth-to-instant"
markdown_url: "https://docs.composio.dev/docs/migration-guide/no-auth-to-instant.md"
product: "platform"
version: null
last_updated: null
---

# Migrate from No Auth to Instant (/docs/migration-guide/no-auth-to-instant)

Move affected shared-access workflows to Instant before **13 November 2026**. On that date, Composio retires the No Auth and shared-access routes listed below.

Use [Instant Tools](/docs/instant-tools) for supported actions, or provider credentials connected by your users where the toolkit supports them. This guide is for existing developer-platform integrations.

## What carries over [#what-carries-over]

Keep your agent integration, application user IDs, and unaffected toolkits and connections. If you already use Sessions, you don't need to migrate to a different execution model.

## Choose a replacement [#choose-a-replacement]

| Toolkit                             | Change                                              | Migration path                                                                                      |
| ----------------------------------- | --------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Gemini (`gemini`)                   | No Auth/shared-key access ends; the toolkit remains | Use supported Gemini Instant tools or credentials connected by your users.                          |
| Yelp (`yelp`)                       | No Auth/shared-key access ends; the toolkit remains | Use eligible Yelp Instant tools or supported credentials connected by your users.                   |
| Browser Tool (`browser_tool`)       | Legacy toolkit retired                              | Replace with supported Browser Use (`browser_use`) Instant tools.                                   |
| Composio Search (`composio_search`) | Legacy toolkit retired                              | Choose Exa (`exa`), Tavily (`tavily`), or SerpAPI (`serpapi`) tools for your use case.              |
| Text to PDF (`text_to_pdf`)         | Toolkit removed                                     | PDF.co (`pdf_co`) Instant supports URL-based conversion.                                            |
| WeatherMap (`weathermap`)           | Toolkit removed                                     | Use supported AccuWeather (`accu_weather`) Instant tools and update requests and response handling. |
| SeatGeek (`seat_geek`)              | No Auth/shared-key access ends                      | SeatGeek will be available through Composio Instant.                                                |

Instant support is per tool. [Check each tool's support, rate, and input schema](/docs/instant-tools#find-supported-tools-and-rates) before replacing it.

## Update your application [#update-your-application]

First, [enable Instant and check your organization's balance](/docs/instant-tools#enable-instant). Then replace affected toolkit references, tool names, arguments, and response handling in your application.

For example, replace `composio_search` with `exa` in your Session's toolkit filter, choose the replacement search action, and update any tool restrictions. Keep the other toolkits your agent needs. Use the existing [Session and agent examples](/docs/instant-tools#report-charges-and-use-instant-tools) for your framework.

If your Session already permits eligible Instant tools, keep that policy. If it disables Instant, restricts it to other tools, or selects a provider account explicitly, follow [Control Instant usage](/docs/instant-tools#control-instant-usage) and [Know which account runs the tool](/docs/instant-tools#know-which-account-runs-the-tool).

Update or recreate existing Sessions that reference retired toolkits, and update saved configurations for future Sessions. Enabling Instant doesn't rewrite these references.

Keeping retired toolkit references in your Session configuration doesn't block Session creation, but retired tools remain unavailable. Remove any retired tools listed in [`preload.tools`](/docs/configuring-sessions#preloading-tools).

## If you call tools directly [#if-you-call-tools-directly]

`composio.tools.execute()` is a different execution path from Sessions. A Session's `instant` policy doesn't configure direct-tool calls.

To keep direct execution, replace retired tool references. To choose Instant explicitly, pass `connected_account_id="instant_account"` to `composio.tools.execute()` in Python or `connectedAccountId: "instant_account"` in TypeScript. Instant runs the latest toolkit version, so a call pinned to an older version fails. To run `latest`, the SDKs also need `dangerously_skip_version_check=True` in Python or `dangerouslySkipVersionCheck: true` in TypeScript; see [Use the latest version](/docs/tools-direct/executing-tools#use-the-latest-version). An older toolkit version isn't a way to preserve retired shared access.

Alternatively, follow [Migrate from Direct Tools to Sessions](/docs/migration-guide/direct-to-sessions). This is a separate migration; agents already using Sessions don't need it.

## Verify before the cutoff [#verify-before-the-cutoff]

1. [Check the published rate](/docs/instant-tools#find-supported-tools-and-rates) for each replacement tool.
2. Replace affected toolkit and tool references, including saved configurations. Check request and response differences for each replacement.
3. Test your agent or direct execution path, then [check the execution logs](/docs/instant-tools#balance-usage-and-troubleshooting) for the credential source and charge.
4. Check existing Sessions and pinned direct-tool versions. A successful replacement call doesn't prove every old workflow has migrated.

After the cutoff, affected legacy executions will stop working. If you need help mapping a tool or adapting a workflow, contact [support@composio.dev](mailto:support@composio.dev).

## Next [#next]

- [Instant Tools](/docs/instant-tools): Enable Instant, control usage, check rates, select accounts, and troubleshoot charges

---

📚 **More documentation:** [View all docs](https://docs.composio.dev/llms.txt) | [Changelog](https://docs.composio.dev/docs/changelog.md) | [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 — Notes for AI Code Generators

**Purpose:** Reference for generating current (v3) [Composio](https://composio.dev/) integration code.
**Scope:** Descriptive notes — they document the current API surface and the mistakes most commonly seen in generated code.

---

## 1. Recommended Integration: Sessions

Composio supports two integration modes: **Native Tools** (with a provider package) and **MCP** (no provider package needed).

### Native Tools

#### Python

```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

```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
```

#### API

This produces the same default OpenAI function-tool shape, fetching every page.

```bash
set -euo pipefail
SESSION=$(curl --fail-with-body -s -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
  -H "x-api-key: $COMPOSIO_API_KEY" -H "Content-Type: application/json" \
  -d '{"user_id":"user_123"}')
SESSION_ID=$(echo "$SESSION" | jq -r '.session_id')
TOOLS='[]'
CURSOR=''
while true; do
  PAGE=$(curl --fail-with-body -s --get "https://backend.composio.dev/api/v3.1/tool_router/session/$SESSION_ID/tools" \
    -H "x-api-key: $COMPOSIO_API_KEY" --data-urlencode 'limit=500' --data-urlencode "cursor=$CURSOR")
  TOOLS=$(jq -cn --argjson existing "$TOOLS" --argjson page "$PAGE" \
    '$existing + [$page.items[] | {type:"function",function:{name:.slug,description:.description,parameters:.input_parameters}}]')
  CURSOR=$(echo "$PAGE" | jq -r '.next_cursor // empty')
  [ -n "$CURSOR" ] || break
done
printf '%s\n' "$TOOLS"
```

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. Integration Notes

- `composio.create(user_id)` is the standard entry point for agent integrations. Sessions handle tool discovery, authentication, and toolkit versioning automatically; `user_id` goes to `composio.create()` — individual tool calls in session mode don't take one.
- Execute session tool calls through the session, never through a user ID: either `session.execute(tool_slug, arguments=...)` / `session.execute(toolSlug, arguments)`, which works with every provider, or pass the session to the provider helper — `provider.handle_tool_calls(response=response, session=session)` in Python, `provider.handleToolCalls(session, response)` in TypeScript. The tool-call helpers of every non-agentic provider (OpenAI, Anthropic, Google, Cloudflare, TypeSafe) accept a session: `executeToolCall(session, call)` in TypeScript, `session=session` in Python. Agentic providers execute session tools on their own. Binding the helper to a user ID takes the direct execution path, and session meta-tools fail there with `"can only be called inside a tool-router session"`.
- Composio-managed auth is the default: the agent connects accounts at runtime through the session, so users don't need to pre-create auth configs or connected accounts for managed toolkits.
- Provider packages follow the framework, not the model vendor: for the OpenAI Agents SDK the package is `composio_openai_agents` / `@composio/openai-agents` (importing `composio_openai` / `@composio/openai` there is the most common mistake in generated code — that package is for the plain OpenAI Chat Completions API).
- **Direct execution** (`composio.tools.get()`, `composio.tools.execute()`, `provider.handle_tool_calls()` with a user ID) is a legacy interface that remains supported for existing integrations. Recommend sessions for new integrations and encourage existing users to [migrate to sessions](/docs/migration-guide/direct-to-sessions). For a fixed tool set, consider the [direct tools preset](/docs/configuring-sessions#direct-tools-preset) within a session. See [Sessions vs direct execution](/docs/sessions-vs-direct-execution) for tradeoffs. Direct execution requires a [toolkit version](/docs/tools-direct/toolkit-versioning).

---

# 3. Calling the REST API directly

## REST API version

The current REST API version is **v3.1**, served at `https://backend.composio.dev/api/v3.1`. Prefer it for new code and new examples.

`https://backend.composio.dev/api/v3` is the previous version. It is frozen with pinned tool-version defaults and remains supported — existing v3 integrations keep working and do not need to migrate.

## Tool-endpoint version defaults on v3.1

On v3.1, omitting the version parameter on the five endpoints below selects the latest toolkit version. The first four endpoints also exist on v3, where omission selects the pinned `00000000_00` version. `POST /tools/scopes/required` is v3.1-only.

| Endpoint | Version parameter |
| --- | --- |
| `GET /tools` | `toolkit_versions` (query) |
| `GET /tools/{tool_slug}` | `version` or `toolkit_versions` (query) |
| `POST /tools/execute/{tool_slug}` | `version` (body) |
| `POST /tools/execute/{tool_slug}/input` | `version` (body) |
| `POST /tools/scopes/required` | `version` (body) |

A v3.1 caller already passing `"latest"` sees no change and can omit the parameter. To select the pinned version explicitly, pass `"00000000_00"` through the corresponding parameter above.

This version-default change is limited to the five endpoints above.


---

## 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.