Contact
One address for corrections to models.rip — a wrong date, a missing grave, a dead source link.
Write to groundskeeper@models.rip. It is read by the person who maintains the archive. There is no ticketing system, no form, and no autoresponder.
What to write about
- A wrong date. A
bornordiedthat does not match the provider’s own page is the most serious error this site can make, and the one most worth reporting. - A missing grave. A model that was generally available, was a named tier, and is now gone — see what gets buried here first, because the bar is deliberately high.
- A model buried too early. If any snapshot of it is still answering in the maker’s own lineup, it is not dead and the grave should be filled in.
- A dead source link. Every date on the site cites a provider page; providers reorganise their docs constantly.
- An epitaph that is wrong about what the model was like. Not that it is unkind — some of them are — but that it is inaccurate.
What makes a correction easy to act on
A link to the provider’s own page carrying the date, and the exact model id as it appeared in the API. Both go straight into the dataset. A correction sourced from a news article or a screenshot generally cannot be used, because every date on this site has to cite the maker.
What happens next
Accepted corrections are edited into the dataset and go live on the next deploy, usually within a few days. The change is visible immediately in /graveyard.json, which is the same data the pages are built from. You will get a reply either way, though not necessarily a fast one — this is a side project, not a service.
Elsewhere
New graves are announced on X and Bluesky. For anything about the API, the dataset or the MCP server, the developer page probably answers it faster than an email will.