Bundled specs

The npm package ships providers/—optional on-disk API descriptions so cold start avoids downloading multi‑MB specs. CLAWQL_PROVIDER selects a single vendor, a merged preset, or interacts with Spec configuration precedence.

Presets and vendors

CLAWQL_PROVIDERNotes
google-top50Merged ~50 curated Google Discovery services
default-multi-providerSame as no spec env: Google top50 + Cloudflare + GitHub
all-providersTop50 plus every other bundled vendor (GitHub, Slack, Sentry, n8n, …)
atlassianJira + Bitbucket merged
googleSingle Discovery example (GKE); use top50 for multi-service
cloudflare, github, slack, sentry, n8n, jira, bitbucketSingle bundled OpenAPI/Discovery per vendor

Aliases: jira / bitbucket map to their standalone bundles; atlassian merges both.

Offline and refresh

Bundled files are read from disk first. If a file is missing, the registry may fetch a fallback URL unless CLAWQL_BUNDLED_OFFLINE=1.

Maintainers refresh specs with npm run fetch-provider-specs (see providers/README.md). Optional GraphQL artifacts: npm run pregenerate-graphql (Bun recommended).

Default first run

With no spec-related environment variables, ClawQL loads default-multi-provider so cross-vendor search works immediately after install.

Was this page helpful?