Wall of Shame
Some specs arrive clean. Some need work.
Every Distilled SDK is generated from the provider's own API description. When that description is wrong — a missing error response, a field marked required that isn't, a type that lies — we fix it with a JSON patch against the spec so the generator can do its job. This page counts those patches.
Ranked by fixes per 100 operations, so a huge API isn't punished for being huge. Providers with no patches at all are in the honour roll below. Numbers come from packages/*/patches at build time.
Honour roll
Zero patches, and used in Alchemy.
Used by real Alchemy resources today and never needed a spec fix. The API description generated a working SDK as published — which is what a spec is supposed to do.
Worst offenders
Most patched, per 100 operations.
- 017,506 moved5,188 replaced4,096 added399 removed12 copied
- 02posthog177.3 fixes / 100 ops2,834 added990 removed1 replaced
- 03212 added17 replaced2 moved
- 04
- 0579 added7 removed4 replaced2 moved
- 06226 added21 replaced1 copied1 removed
- 07
- 08
- 09
- 10
- 11
- 1281 replaced27 added
- 13
- 141,894 declared
- 15forgejo5.2 fixes / 100 ops24 added1 moved1 replaced
- 16
- 175 added1 replaced
- 18
- 192 added1 tested1 replaced
- 20
Not yet exercised
Zero patches, zero evidence.
63 more providers have no patches, but no consumer has leaned on them yet. A clean sheet here means untested, not correct — they move up once something real depends on them.
- azure13499 ops
- ovh4139 ops
- infisical2298 ops
- datadog1690 ops
- github1187 ops
- stackit988 ops
- elasticsearch812 ops
- okta730 ops
- google-workspace708 ops
- metabase653 ops
- digitalocean639 ops
- zendesk636 ops
- auth0477 ops
- mongodb-atlas459 ops
- vercel408 ops
- launchdarkly389 ops
- whop388 ops
- growthbook363 ops
- hostinger355 ops
- expo-eas343 ops
- vanta339 ops
- huggingface324 ops
- slack317 ops
- plaid305 ops
- remote279 ops
- apache-superset276 ops
- coolify275 ops
- daytona274 ops
- modal251 ops
- grafana250 ops
- clerk235 ops
- intercom231 ops
- sentry221 ops
- render200 ops
- opencode187 ops
- polar186 ops
- customerio172 ops
- redis-cloud164 ops
- chronosphere149 ops
- coinbase146 ops
- meilisearch142 ops
- gusto133 ops
- doppler128 ops
- paypal115 ops
- argocd106 ops
- docker106 ops
- temporal104 ops
- unkey85 ops
- porkbun84 ops
- resend79 ops
- modrinth76 ops
- mercury72 ops
- xata67 ops
- boat-dev65 ops
- trigger-dev61 ops
- squarespace53 ops
- inngest50 ops
- adyen28 ops
- s224 ops
- archil23 ops
- spacetimedb18 ops
- onepassword15 ops
- turbopuffer14 ops
Method — how this is counted
- A fix is one JSON Patch operation (
add,replace,remove,move, …) in a file underpackages/<provider>/patches/. For AWS, whose patches are declarative, each named operation, structure or error entry counts as one. - An operation is one generated SDK call — an exported
OperationMethodinsrc/services/. - Patches are how we keep SDKs correct without editing generated code; they survive regeneration. A high count says something about the spec, not the provider's API.
- Used in Alchemy means an Alchemy resource imports the package on
main— read from Alchemy'spackage.jsonat build time (checked 2026-09-20). Zero patches on a package nobody consumes is not counted as clean. - Think a count is wrong? Open an issue in alchemy-run/distilled. When a provider fixes its description upstream, the patch goes away.