Back to Browse
Annalist AI Model Retirement Calendar
x402
Annalist AI Model Retirement Calendar is a paid API for AI agents from api.annalist.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-21).
Returns shutdown dates, deprecation states, and recommended replacements for AI models across Anthropic, OpenAI, Amazon Bedrock, Azure, Vertex, and Gemini platforms, tracked daily so date changes are visible.
Price / call$0.005
Success—
StatusUnknown
How this service works
Retirement calendar for AI models across platforms: shutdown dates, 'not sooner than' floors, states and recommended replacements from the official Anthropic, OpenAI and Amazon Bedrock deprecation pages, plus Azure, Vertex, Gemini and others, recorded daily so moved dates show. The same model often retires on different dates on different platforms. One model with model=, or upcoming shutdowns. Signed.
Output
A signed JSON response containing, for each matching model, the shutdown date, any 'not sooner than' floor date, the deprecation state, the platform(s) it applies to, and the recommended replacement model if one has been announced. Multiple entries may be returned when the same model retires on different dates across platforms.
Example use cases
Check model retirement before deployment
“I'm about to deploy an app using gpt-4o — can you check when it's being retired on OpenAI and whether there's a recommended replacement I should plan for?”
Alert on upcoming shutdowns in 30 days
“Show me all AI models that are shutting down within the next 30 days across any platform so I can update my integrations.”
Compare cross-platform retirement dates
“Look up when claude-3-opus retires — I want to know the date on Anthropic directly versus on Amazon Bedrock, since I've heard they can differ.”
Technical details
Endpoint
GEThttps://api.annalist.dev/v1/ai/retirements?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need authoritative, cross-platform AI model deprecation data sourced directly from official Anthropic, OpenAI, Amazon Bedrock, Azure, Vertex, and Gemini deprecation pages. It is the right choice when you need to compare retirement dates for the same model across platforms (which frequently differ), when you need signed data for auditability, or when you want daily-resolution tracking so you can detect when providers silently move retirement dates. Prefer it over scraping provider docs yourself or relying on stale cached sources.
Side effects
- Model ID fragment too vague — returns too many or no matches
- Platform filter misspelled or unsupported — empty results
- Days parameter outside 1–365 range — validation error
- No upcoming retirements in the requested window — empty list returned
- Payment not completed via x402 — 402 response blocking data access
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"