How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us

API Commons Deprecation Policy

An API Commons schema for publishing a provider’s deprecation policy layer as machine-readable data. Minimum notice, support window per version, announcement channels, and use of the Deprecation (RFC 9745) and Sunset (RFC 8594) headers, as data.

The API Commons Deprecation Policy schema is one of eight business layers that make the political side of an API machine-readable, beside the technical contract. Minimum notice, support window per version, announcement channels, and use of the Deprecation (RFC 9745) and Sunset (RFC 8594) headers, as data.

It profiles existing work rather than inventing: see RFC 9745 and RFC 8594. Generated documents for catalog providers are stamped with x-apis-io-derivation and live in each provider’s repository; the schema, under Apache 2.0, is at github.com/api-commons/deprecation-policy.

Background: The Technical Side Translated. The Business Side Did Not.

Industry: api-specification

Resources

GitHub GitHub License License
#API Commons #Business #Machine-Readable #Schema
← Back to all Standards
Standard Details
Slug api-commons-deprecation-policy
Governing body API Commons
Schema access Open — fetched at source

providers on APIs.io were observed implementing this, measured .

Specification facts verified 2026-11-09.

Explore more

Navigate related API building blocks.

All Standards Schemas Rules Policies
Discover APIs
apis.io — API Search

Search across thousands of APIs on apis.io →

Work with this as data

Every standard here is available over the API and to AI agents over MCP.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for standards
8 tools reach this content
  • find_building_blocksBrowse every standards entry — call it with type="standards".
  • get_building_blockOne standards entry in full; add include=content for the body (Pro).
  • standard_adoptionHow far a standards body actually got — repos published, how many graduated.
  • standard_coalitionWho is behind a standard: governing bodies, working groups, member companies, people.
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
This standard 
curl "https://api.apievangelist.com/v1/standards/api-commons-deprecation-policy"
Full body (Pro) 
curl "https://api.apievangelist.com/v1/standards/api-commons-deprecation-policy?include=content" \
  -H "x-api-key: $AE_KEY"
Related across the network 
curl "https://api.apievangelist.com/v1/standards/api-commons-deprecation-policy/related"
All standards 
curl "https://api.apievangelist.com/v1/standards?limit=25"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account