Reference page routes and examples need comparison.
Provider migration
Migrate from Scalar to Sourced
Scalar gives teams a modern API reference surface. Sourced adds SDK generation, migration reporting, and publishing workflows around the same OpenAPI source. On this page: what to scan in your Scalar setup, the migration checks Sourced runs, and a preview of the generated SDK and docs you would get.
Unlimited previews. No credit card required.
01Checks
What to check
Interactive client behavior may differ.
SDK package shape needs a separate compatibility pass.
Custom docs content needs a migration inventory.
02Checks
Migration checklist
Export the OpenAPI source and any Scalar-specific configuration.
Compare auth, examples, and model rendering against Sourced docs preview.
Run SDK compatibility checks before package publishing.
Map Scalar reference URLs to Sourced docs URLs for redirects.
Keep preview pages private until the release report is accepted.
03Details
Why Sourced fits
Sourced turns the spec into docs plus SDK artifacts, not only reference pages.
Release readiness is visible in the dashboard.
Docs preview and SDK preview move together.
Honest trade-off: if your priority is a polished standalone API reference component, Scalar may remain a strong fit.