Scalar's entry paid tier is $150/mo ($125/mo billed yearly); Bump.sh's entry paid tier is $50/mo — roughly a third of the price. But they cap different things: Scalar's Pro plan caps API count and endpoints per SDK, while Bump.sh's Basic plan caps API docs count and MCP tools. The right comparison is per-limit, not per-sticker-price. Every number below was read directly from each vendor's own pricing page on 2026-09-16.
What do Scalar and Bump.sh cost? (verified table)
Scalar: free, then $150/mo (Pro), $600/mo (Business) or custom. Bump.sh: no free tier (Pro has a 14-day trial), $50/mo (Basic), $120/mo (Pro) or custom.
| Tier | Scalar | Bump.sh |
|---|---|---|
| Free | $0 — up to 3 APIs, 1 SDK (≤25 endpoints), 1 editor seat, 50 Agent credits | Not published as a distinct free self-serve tier — open source projects qualify for free Pro access (contact required) |
| Entry paid | Pro: $150/mo ($125/mo billed yearly, $1,500/yr) — up to 15 APIs, 1 SDK (≤100 endpoints), 5 seats, 500 Agent credits, custom domains, Git Sync, MCP servers | Basic: $50/mo — 10 API docs, 5 MCP tools, 3 internal users, 20 external users, OpenAPI/AsyncAPI/Arazzo support, custom domain |
| Mid paid | Business: $600/mo ($500/mo billed yearly, $6,000/yr) — up to 25 APIs, 1 SDK (≤250 endpoints), 10 seats, SSO/SAML, subpath hosting | Pro: $120/mo — 30 API docs, 50 MCP tools, 5 internal users, 40 external users, branch management, private MCP servers, changelog automation |
| Top tier | Enterprise: custom — unlimited APIs, custom SDK sizing, full RBAC, priority support, dedicated Slack/Teams channel | Custom: not published (contact sales) — unlimited users, SSO, on-prem MCP dataplane, 99.99% SLA |
| Extra SDKs | $150/mo each on Pro; $600/mo each on Business (volume discounts available) | Not applicable — Bump.sh doesn't sell SDK generation as an add-on |
Sources, fetched 2026-09-16: scalar.com/pricing, bump.sh/pricing.
What does each price actually buy you?
Scalar's price scales with API/SDK/endpoint count and includes an API client and SDK generation in the same tier; Bump.sh's price scales with API docs count and MCP tool count, and doesn't include SDK generation at all — it's a docs, changelog, and API-hub product. If you need generated client SDKs as part of the plan, Scalar's Pro tier includes one; on Bump.sh you'd need a separate SDK generator regardless of which plan you pick.
If your bottleneck is API count
Bump.sh Basic covers 10 API docs for $50/mo; matching that on Scalar means either staying on the 3-API free tier (not enough) or paying $150/mo for up to 15 APIs. For teams publishing docs for many small internal or partner APIs, Bump.sh's per-doc economics are the cheaper path.
If your bottleneck is MCP tool count
Bump.sh explicitly meters MCP tools (5 on Basic, 50 on Pro) as a first-class limit; Scalar doesn't cap MCP tools by number — it bundles "ship docs, SDKs, and MCP servers" under the same API/SDK caps starting at Pro ($150/mo). If you're generating a large MCP surface from OpenAPI and want it billed separately from your docs/SDK caps, check Bump.sh's per-tool ceiling against your actual operation count before committing.
If your bottleneck is endpoints per API
Scalar's per-SDK endpoint caps (25 free / 100 Pro / 250 Business) are the tightest constraint in this table for a single large API. Bump.sh doesn't publish an endpoint-count limit on its pricing page — its caps are doc/tool/user counts, not endpoint counts within a doc.
What does neither vendor publish?
Neither page lists per-seat overage pricing, and Bump.sh's Custom tier and Scalar's Enterprise tier are both "contact sales" with no published number — consistent with how most usage-based dev-tools pricing works above the self-serve tiers. Don't estimate a number for either; ask sales for your actual usage profile.
Which one should you pick?
Pick by what you're actually shipping, not by the sticker price: Scalar if SDK generation and an in-page API client matter as much as docs; Bump.sh if you're publishing many APIs' worth of docs and changelogs and will source SDKs elsewhere. Both are still just docs-and-related-tooling platforms — neither publishes the release-readiness or SDK-compatibility-diff step that a full OpenAPI-to-SDK-and-docs pipeline needs before a package reaches npm or PyPI. See our full parity notes in migrate from Scalar and migrate from Bump.sh, or start a free Sourced report to see generated docs and SDK previews from your own OpenAPI spec before comparing invoices.