The Wall of Shame
If your api is on this list: fix your spec
Every generated SDK: ours, the vendor's, the one you'd write; is only ever as good as the api spec its built from. Most of these specs aren't generated from the source and regularly drift from the actual implementation. We maintain a list of who we have to patch the most so we can hopefully pressure these providers to fix their source of truth.
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; A HUGE thank you to the providers we don't have to patch. Numbers come from packages/*/patches at build time.
Honour roll
Zero patches, and used in Alchemy.
Used by real Alchemy resources today and don't need their spec fixed. The API spec generated a working SDK as published; which is what a spec is supposed to do.
- Nobody. Every package Alchemy uses has needed at least one spec fix. The bar is here; nobody has cleared it yet.
Worst offenders
Most patched, per 100 operations.
- 017,603 moved5,249 replaced4,893 added632 removed12 copied
- 02
- 03technitium309.4 fixes / 100 ops378 added13 replaced2 removed
- 04posthog234.0 fixes / 100 ops5,125 removed996 added9 moved6 replaced
- 05270 added21 removed16 replaced4 moved
- 06convex163.3 fixes / 100 ops103 added18 replaced8 removed
- 0775 added61 removed7 replaced
- 08
- 09
- 10doppler136.0 fixes / 100 ops127 added43 removed16 replaced3 moved
- 11tailscale109.7 fixes / 100 ops91 added8 removed3 replaced
- 12
- 13
- 14
- 15
- 16daytona85.1 fixes / 100 ops221 added8 removed4 tested2 replaced
- 17
- 18questrade68.0 fixes / 100 ops8 removed5 copied4 moved
- 19
- 20
- 21forgejo40.9 fixes / 100 ops190 added10 replaced3 moved
- 22
- 23
- 2457 added2 moved
- 2574 removed17 added2 replaced
- 26
- 27
- 28
- 29gcp23.6 fixes / 100 ops3,265 added18 removed1 replaced
- 30
- 31
- 32
- 33digitalocean13.8 fixes / 100 ops82 added22 removed18 replaced
- 34azure13.1 fixes / 100 ops1,095 replaced696 added18 removed4 moved
- 35
- 361,945 declared
- 37anthropic9.1 fixes / 100 ops26 added6 replaced2 removed
- 3810 added1 replaced
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46github1.0 fixes / 100 ops10 added1 replaced1 removed
- 47
- 484 added1 replaced
Not yet exercised
Zero patches, zero evidence.
60 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.
- tencentcloud15381 ops
- ovh4692 ops
- infisical2527 ops
- datadog1929 ops
- stackit1038 ops
- elasticsearch819 ops
- metabase728 ops
- okta722 ops
- google-workspace708 ops
- zendesk672 ops
- dokploy639 ops
- auth0490 ops
- mongodb-atlas488 ops
- whop451 ops
- hostinger421 ops
- growthbook419 ops
- vanta400 ops
- mailchimp393 ops
- launchdarkly387 ops
- huggingface376 ops
- slack355 ops
- apache-superset328 ops
- expo-eas322 ops
- gusto321 ops
- plaid303 ops
- remote303 ops
- coolify291 ops
- sentry283 ops
- grafana250 ops
- clerk248 ops
- render247 ops
- intercom237 ops
- polar194 ops
- coinbase178 ops
- porkbun177 ops
- redis-cloud174 ops
- opencode169 ops
- customerio161 ops
- chronosphere149 ops
- revenuecat141 ops
- paypal115 ops
- unkey113 ops
- s3112 ops
- argocd106 ops
- docker106 ops
- temporal104 ops
- mercury89 ops
- trigger-dev85 ops
- xata80 ops
- resend79 ops
- modrinth76 ops
- inngest75 ops
- notion62 ops
- squarespace53 ops
- iceberg34 ops
- adyen30 ops
- s224 ops
- celld22 ops
- spacetimedb18 ops
- turbopuffer16 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 an SDK is kept 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-17, cached). 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 spec upstream, the patch goes away.