Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
OpenAPI Scripts
fetch-with-retry.ts
Shared fetchWithRetry helper used by the toolkit generator and parity checker.
It wraps the global fetch
with rate-limit-aware retry/backoff: it retries 429 and transient 5xx
responses, honors the Retry-After header when present, otherwise falls back to
exponential backoff with jitter, and caps attempts so CI still fails fast when
the backend is genuinely down.
This matters because generate-toolkits.ts issues ~6500 requests per run
(a few catalog pages + 3 per toolkit across a ~2.1k catalog), which can exceed
the backend request limit.
Meta-tools reference
bun run generate:meta-tools renders the reference from
public/data/meta-tools.json. Set COMPOSIO_META_TOOLS_SCHEMA_URL to the
production Platform HTTPS export to update the snapshot before rendering. The
export must return the same JSON array format as the snapshot. Docs - Update Data
reads the URL from the repository variable of the same name. With the variable
unset, reference pages use the checked-in schema version.
Toolkit versions
generate-toolkits.ts owns the complete toolkit catalog and always sources it
from the production API. For a version-only repair, run the narrower generator:
COMPOSIO_API_KEY=... bun run generate:toolkit-versions
Both paths share toolkit-versions.ts, so they fetch and apply changelog values
with identical semantics: a toolkit missing from the production changelog gets
version: null. Any COMPOSIO_API_BASE override must normalize to
https://backend.composio.dev/api/v3; non-production sources fail before a
request is made.
fetch-openapi.mjs
Fetches the Composio OpenAPI spec and filters it for use in Fumadocs API reference documentation.
Usage
bun run scripts/fetch-openapi.mjs
This outputs public/openapi.json which is used by lib/openapi.ts.
Why Filtering is Needed
The raw OpenAPI spec from https://backend.composio.dev/api/v3/openapi.json has issues that break documentation generators:
- Endpoints with multiple tags - Causes duplicate entries in sidebar
- Internal endpoints exposed - CLI, Admin, Profiling endpoints shouldn't be in public docs
See OPENAPI_IMPROVEMENTS.md in the fumadocs root for planned fixes to the spec itself.
What Gets Filtered
Ignored Paths
These endpoints are completely removed:
- /api/v3/mcp/validate/{uuid}
- /api/v3/cli/get-session
- /api/v3/cli/create-session
- /api/v3/auth/session/logout
Ignored Tags
Endpoints with only these tags are removed:
- CLI
- Admin
- Profiling
Duplicate Prevention
If an endpoint has multiple tags, only the first tag is kept. This prevents the same endpoint appearing in multiple sidebar sections.
Configuration
The script uses environment variables:
| Variable | Default | Description |
|---|---|---|
OPENAPI_SPEC_URL |
https://backend.composio.dev/api/v3/openapi.json |
Source OpenAPI spec URL |
For staging deployments, set:
bash
OPENAPI_SPEC_URL=https://staging.composio.dev/api/v3/openapi.json
verify-kb.ts
Checks published KB guides against the production data this repo already
refreshes. Runs inside docs-update-data.yml right after the catalog and
OpenAPI specs are regenerated, so freshness is verified on every production
deploy instead of on a review calendar.
bun run verify:kb # catalog checks only, no network
bun run verify:kb --check-links # also probe provider doc links
bun run verify:kb --json # machine-readable report
bun run verify:kb --markdown out.md # write the report to a file
Exits non-zero when any finding is an error. --warnings-as-errors promotes
warnings too. See docs/decisions/kb-freshness-verification.md for what is
checked and why placeholders, bare URLs, and 5xx responses are excluded.
A guide that deliberately cites a removed identifier declares it in
verifyIgnoreToolSlugs in its kb/guides/<slug>.json.