Organization name, docs URL, and support contact.
Config audit
Turn stainless.yml into a migration map.
Your Stainless config explains what the generated SDKs and docs are supposed to look like. Bloom turns it into a readable migration plan.
Config
Fields to preserve
Targets, package names, production repos, npm/PyPI publishing settings.
Resources, subresources, method names, and model mappings.
Client auth settings and environment variable names.
Config
Fields that need review
Custom README examples.
MCP server settings.
Disabled mock tests.
Any endpoint present in config but missing from OpenAPI.
Example output
The config migration page uses Sendblue's real stainless.yml shape.
TypeScript, Python, and MCP settings are all present in Sendblue config.
`SENDBLUE_API_API_KEY` and `SENDBLUE_API_API_SECRET` must survive migration.
Messages, contacts, webhooks, media, TOTP, seats, lines, and more.
`retrieve_opt_out_status` is configured but missing from the source OpenAPI.
| Example | Why it matters | Current result |
|---|---|---|
| stainless.yml | Defines package names, production repos, publishing settings, resources, methods, auth, readme examples, and MCP host. | Parseable into a migration map. |
| OpenAPI/config comparison | Detects methods configured in Stainless but absent from source OpenAPI. | 1 skipped configured method requires review. |
Related pages