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.
- 01resend693.5 fixes / 100 ops935 added11 removed11 replaced
- 027,601 moved5,251 replaced4,916 added634 removed12 copied
- 03
- 04technitium309.4 fixes / 100 ops378 added13 replaced2 removed
- 05convex248.1 fixes / 100 ops170 added18 replaced8 removed
- 06posthog234.0 fixes / 100 ops5,125 removed996 added9 moved6 replaced
- 07263 added22 removed17 replaced4 moved1 tested
- 0875 added61 removed7 replaced
- 09
- 10
- 11doppler136.0 fixes / 100 ops127 added43 removed16 replaced3 moved
- 12
- 13boat-dev124.1 fixes / 100 ops139 added3 removed2 replaced
- 14tailscale109.7 fixes / 100 ops91 added8 removed3 replaced
- 15
- 16
- 17
- 18daytona85.1 fixes / 100 ops221 added8 removed4 tested2 replaced
- 19clickhouse-cloud77.3 fixes / 100 ops96 added21 replaced17 moved6 removed
- 20
- 21questrade68.0 fixes / 100 ops8 removed5 copied4 moved
- 22digitalocean64.5 fixes / 100 ops549 added24 removed23 replaced
- 23341 added2 replaced
- 24
- 25inngest46.7 fixes / 100 ops31 added6 removed5 replaced
- 26
- 27forgejo40.9 fixes / 100 ops190 added10 replaced3 moved
- 28
- 29
- 3057 added2 moved
- 3174 removed17 added2 replaced
- 32
- 33
- 34
- 354,781 added155 removed73 copied11 replaced
- 36
- 37gcp23.6 fixes / 100 ops3,267 added16 removed1 replaced
- 38
- 39
- 40
- 41scaleway12.6 fixes / 100 ops130 added35 replaced34 copied
- 42starburst-galaxy11.2 fixes / 100 ops18 added4 removed1 replaced
- 43
- 44anthropic10.7 fixes / 100 ops32 added6 replaced2 removed
- 45azure8.5 fixes / 100 ops1,061 replaced96 added14 removed4 moved
- 46
- 4710 added1 replaced
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57github1.0 fixes / 100 ops10 added1 replaced1 removed
- 58
Not yet exercised
Zero patches, zero evidence.
56 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
- gusto321 ops
- plaid303 ops
- remote303 ops
- coolify291 ops
- sentry283 ops
- grafana250 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
- modrinth76 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.