@devries-cameron20 / composio Mirror · read-only / commits / 92b110e4e
Fork 0

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, 07:15 UTC

docs: add No Auth to Instant migration guide

Shashwat Singh committed Oct 28, 2026 at 17:18 UTC 92b110e4eee2f7faaa59416cd27df627f1f1953e
3 files changed +103
docs/content/docs/migration-guide/index.mdx
+6
@@ -7,6 +7,12 @@ written: "December 2025"
7 ## Available migration guides
8
9 <Accordions>
10 + <Accordion title="Migrate from No Auth to Instant">
11 + Move shared-access workflows to Instant with your existing agents and Sessions.
12 +
13 + [View No Auth to Instant migration guide →](/docs/migration-guide/no-auth-to-instant)
14 + </Accordion>
15 +
16 <Accordion title="Migrating from Direct Tools to Sessions">
17 Move from manual tool fetching and execution to the sessions paradigm. Your existing auth configs and connected accounts carry over.
18
docs/content/docs/migration-guide/meta.json
+1
@@ -1,6 +1,7 @@
1 {
2 "title": "Migration guides",
3 "pages": [
4 + "no-auth-to-instant",
5 "direct-to-sessions",
6 "mcp-servers-to-sessions",
7 "tool-router-beta",
docs/content/docs/migration-guide/no-auth-to-instant.mdx new
+96
@@ -0,0 +1,96 @@
1 +---
2 +title: Migrate from No Auth to Instant
3 +description: Move shared-access workflows to Instant with your existing agents and Sessions
4 +keywords: [No Auth, Instant, migration, Sessions, shared access]
5 +---
6 +
7 +Use Instant to run supported tools on Composio's provider accounts, charged to your organization's Composio balance. Your users don't need separate provider credentials for those tools.
8 +
9 +From **13 November 2026**, the shared-access routes below are being retired. This change supports growing usage while maintaining performance and quality for web search, browsing and AI tools via Composio.
10 +
11 +## Update your Session
12 +
13 +First, [enable Instant in project Settings and fund your organization's balance](/docs/instant-tools#enable-instant). If your agent already uses Sessions, keep your agent integration and change only the affected toolkit references and any Instant restrictions.
14 +
15 +For example, replace the legacy `composio_search` toolkit with `exa`:
16 +
17 +<Tabs groupId="language" items={['Python', 'TypeScript', 'API']} persist>
18 +<Tab value="Python">
19 +```python
20 +from composio import Composio
21 +
22 +composio = Composio()
23 +session = composio.sessions.create(
24 + user_id="user_123",
25 + toolkits=["exa"],
26 + instant={"toolkits": {"enable": ["exa"]}},
27 +)
28 +tools = session.tools()
29 +```
30 +</Tab>
31 +<Tab value="TypeScript">
32 +```typescript
33 +import { Composio } from "@composio/core";
34 +
35 +const composio = new Composio();
36 +const session = await composio.create("user_123", {
37 + toolkits: ["exa"],
38 + instant: { toolkits: { enable: ["exa"] } },
39 +});
40 +const tools = await session.tools();
41 +```
42 +</Tab>
43 +<Tab value="API">
44 +```bash
45 +SESSION_ID=$(curl -s -X POST https://backend.composio.dev/api/v3.1/tool_router/session \
46 + -H "x-api-key: $COMPOSIO_API_KEY" \
47 + -H "Content-Type: application/json" \
48 + -d '{"user_id":"user_123","toolkits":{"enable":["exa"]},"instant":{"toolkits":{"enable":["exa"]}}}' \
49 + | jq -r '.session_id')
50 +
51 +curl -X GET https://backend.composio.dev/api/v3.1/tool_router/session/$SESSION_ID/tools \
52 + -H "x-api-key: $COMPOSIO_API_KEY"
53 +```
54 +</Tab>
55 +</Tabs>
56 +
57 +Pass `tools` to your existing agent as usual, using your framework's [provider adapter](/docs/providers). Your agent can discover and execute eligible Exa tools. This example permits Instant only for Exa; include your other required toolkits in the top-level filter and adjust the Instant filter to match your spending policy.
58 +
59 +Omitting `instant` permits eligible Instant usage when the project setting is on. You don't need to add an `instant` object if your current Session already allows it. A Session with `instant=false`, restrictive filters, or an explicit provider-account selection needs a corresponding policy or account change. See [Instant controls](/docs/instant-tools#control-instant-usage).
60 +
61 +Existing Sessions can use Instant after project enablement unless their policy prevents it. Update or recreate Sessions that still reference retired toolkits, and update saved Session configurations so future Sessions use the replacements too. Enabling Instant doesn't rewrite tool slugs, arguments, or response handling.
62 +
63 +## Choose a replacement
64 +
65 +All changes in this table take effect on **13 November 2026** for the developer platform.
66 +
67 +| Toolkit | Change | Migration path |
68 +| --- | --- | --- |
69 +| Gemini (`gemini`) | No Auth/shared-key access ends; the toolkit remains | Use supported Gemini Instant tools or credentials connected by your users. |
70 +| Yelp (`yelp`) | No Auth/shared-key access ends; the toolkit remains | Use eligible Yelp Instant tools or supported credentials connected by your users. |
71 +| Browser Tool (`browser_tool`) | Legacy toolkit retired | Replace with supported Browser Use (`browser_use`) Instant tools. |
72 +| Composio Search (`composio_search`) | Legacy toolkit retired | Choose Exa (`exa`), Tavily (`tavily`), or SerpAPI (`serpapi`) tools for your use case. |
73 +| Text to PDF (`text_to_pdf`) | Toolkit removed | PDF.co (`pdf_co`) Instant supports URL-based conversion. Inline text/Markdown workflows require adaptation. |
74 +| WeatherMap (`weathermap`) | Toolkit removed | Use supported AccuWeather (`accu_weather`) Instant tools and update requests and response handling. |
75 +| SeatGeek (`seat_geek`) | No Auth/shared-key access ends | SeatGeek will be available through Composio Instant. |
76 +
77 +Instant eligibility is per action. [Check each tool's support, rate, and input schema](/docs/instant-tools#find-supported-tools-and-rates) before replacing it. These alternatives aren't interchangeable APIs. In particular, PDF.co URL conversion isn't a drop-in replacement for inline text or Markdown rendering.
78 +
79 +## If you call tools directly
80 +
81 +`composio.tools.execute()` is a different execution path from `session.execute()`, `session.tools()`, or a Session MCP endpoint. A Session's `instant` policy doesn't configure direct-tool calls.
82 +
83 +If you want to keep direct execution, replace retired tool references, check the target action's Instant support on the version you use, and select `connected_account_id="instant_account"` in Python or `connectedAccountId: "instant_account"` in TypeScript when choosing Instant explicitly. Keep direct-tool [version pinning](/docs/tools-direct/toolkit-versioning) in place. An older version isn't a way to preserve retired shared access.
84 +
85 +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.
86 +
87 +Where supported, your users can connect their own provider credentials instead. Composio normally selects your user's connection before Instant. To choose Instant explicitly within a Session, use its [account selection options](/docs/instant-tools#inspect-or-explicitly-select-an-instant-account). Account selection still requires project permission, Session permission, and tool eligibility.
88 +
89 +## Verify before the cutoff
90 +
91 +1. Check [Instant pricing](https://composio.dev/pricing), enable the project setting, and check the organization's funded balance.
92 +2. Replace affected toolkit and action references, including saved configurations. Check request and response differences for each replacement.
93 +3. Test your agent or direct execution path. Inspect the [execution logs](/docs/instant-tools#balance-usage-and-troubleshooting) for the credential source and charge; an absent charge isn't proof that a call was free.
94 +4. Check existing Sessions and pinned direct-tool versions. A successful replacement call doesn't prove every old workflow has migrated.
95 +
96 +After the cutoff, affected legacy executions will stop working. If you need help mapping an action or adapting a workflow, contact [support@composio.dev](mailto:support@composio.dev).