Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: tighten toolkit version callout
Kshitij Jhunjhunwala committed
Aug 10, 2026 at 19:21 UTC
3165e82ec9b2c61630db85f72bade3301bfb3544
2 files changed
+2
-2
docs/content/docs/tools-direct/fetching-tools.mdx
+1
-1
@@ -242,7 +242,7 @@ const toolkitSearchRaw = await composio.tools.getRawComposioTools({
242
</Tabs>
243
244
<Callout type="info">
245
-These SDK examples use `latest`, the default when you don't configure `toolkit_versions` (TypeScript: `toolkitVersions`) on the client. For direct REST calls, omission depends on the API version: the v3 tools endpoints default to the pinned base version (`00000000_00`), while the v3.1 tools endpoints default to `latest`. Use `latest` when an LLM consumes tool output; pin a dated version when application code parses the output. See [toolkit versioning](/docs/tools-direct/toolkit-versioning).
245
+These SDK examples use `latest` by default. REST v3 tool endpoints default to `00000000_00`; REST v3.1 tool endpoints default to `latest`. Pin a dated version when application code parses tool output. See [toolkit versioning](/docs/tools-direct/toolkit-versioning).
246
</Callout>
247
248
## Next
docs/tests/static/content.test.ts
+1
-1
@@ -140,7 +140,7 @@ describe("Content - toolkit version guidance", () => {
140
test("the SDK fetching guide distinguishes SDK, REST v3, and REST v3.1 defaults", async () => {
141
const content = await readFile(FETCHING_TOOLS_DOC, "utf-8");
142
143
- expect(content).toContain("don't configure `toolkit_versions` (TypeScript: `toolkitVersions`)");
143
+ expect(content).toContain("These SDK examples use `latest` by default");
144
expect(content).toContain("v3 tools endpoints default to the pinned base version (`00000000_00`)");
145
expect(content).toContain("v3.1 tools endpoints default to `latest`");
146
expect(content).not.toMatch(/the API returns tools from the base version/i);