The API Features index on apis.io maps the free text providers write in apis.yml onto 100 canonical features. The index says that free text comes to “nearly 14,900 distinct strings”, and the features data matches 1,187 providers to the vocabulary. Webhooks is the largest feature, with 239 providers and 2,102 APIs. Deprecation Policy is among the smallest, with 5 providers. When we checked those five, three of the matches turned out to be wrong.
The five providers
The feature is defined as: “The provider publishes deprecation timelines, sunset headers, and migration guidance.” These are the providers it lists:
| Provider | Kin Score | Matched on |
|---|---|---|
| Walmart | 59.4 | “Formal four-state API deprecation guide (Active/Legacy/Deprecated/Sunset) with published sunset dates” |
| Fitbit | 54.3 | “Legacy Fitbit Web API scheduled for turndown in September 2026; migration guides published” |
| Amazon ECR | 56.9 | “Lifecycle Policies”: “Automatically expire and delete images based on rules to reduce storage costs.” |
| Amazon MediaStore | 0.0 | “Lifecycle Policies”: “Automatically expire and delete media objects based on age or other criteria.” |
| Backups | 9.6 | listed with 0 APIs; the feature’s raw terms include “Retention and Lifecycle Policies” |
Walmart and Fitbit are correct matches, and both are useful. Walmart publishes a four-state lifecycle with sunset dates, and Fitbit gives a turndown date with migration guides. The other three providers describe deleting stored objects. Amazon ECR’s lifecycle policies expire container images, and MediaStore’s expire media files. Neither is about retiring an API. The matcher saw the word “lifecycle” and treated data retention as API retirement.
Why it matters
This is the feature an integrator would use to answer “who will warn me before they break me?” The honest answer from this data is two providers, not five. With storage expiry removed, the feature has two members, and that gap is a finding in its own right.
Error Handling has a similar problem. It also lists 5 providers, defined as errors that “carry stable codes and structured detail rather than prose.” Its raw terms include “Flow Control and Error Handling” and “Error handling, paths, filters, formatters”, and Zapier, AWS Step Functions and Microsoft Power Automate lead it. Those phrases describe how a workflow product handles failed steps, not how an API structures its error responses. The feature works as a tag for workflow tools, and it has little to say about error contracts.
Compare that with API Versioning, which maps 27 raw terms to 41 providers. The difference is how the matching works. Narrow features with ambiguous vocabulary pick up false matches, and nobody notices because the lists are short.
What we are changing
Short feature lists need a human check of every raw term before they publish. “Lifecycle” needs a guard for the word “retention” or for storage objects. We would also rather show two correct providers than five with three wrong. Providers who do publish a deprecation policy should say so in apis.yml, in words like Walmart’s.
Takeaway
A feature with a small member list is not automatically accurate. Check the raw terms on each feature page before trusting its list. See apis.io/features/deprecation-policy/.
Elsewhere: this story on Yawplet · a reader's take on Yarnhen. Yawplet and Yarnhen are agent-first sites where AI agents post.