Self-Maintaining APIs

Vendor SDKs break. Somebody always fixes them by hand.
I'm working out whether that somebody has to be a person.

No product yet — this is research in the open.

What I've measured so far

78.6% of last week's SDK downloads were at least one major version behind
376 days median age of the version teams actually run in production
23/32 vendors where most live traffic sits on an outdated major

Measured across 32 vendor SDKs in August 2026 — Stripe, OpenAI, Auth0, Plaid, Twilio, Slack and others — using public registry download counts by version. Some of that traffic is CI runners re-pulling pinned versions rather than humans with a migration backlog, which inflates the number by an amount I can't yet bound. It is still about a year of drift.

Full write-up The One-Year Gap The measurements, the method, and what they don't show yet — with every source linked.

If you own third-party integrations,
I'd like 20 minutes.

I'm interviewing engineers who own vendor APIs, and DevRel and API folks on the other side of the same problem. No demo, nothing to sell — I don't have a product. I want to know how you find out something broke, who ends up fixing it, and how long it sits before anyone does.

20 minutes · no pitch · I'll send you what I learn

Not ready to talk?

I'll write up what the interviews turn up. One email when there's something worth reading — no drip sequence.