LLM Price & Lifecycle Archive
Dated archive of LLM prices, context windows, announced retirement dates and quiet delistings across 400+ models and 50+ providers.
POST /v1/model/archive · 1 credit
- No account needed to try any endpoint on this page.
- Deterministic endpoints answer from cache in single-digit milliseconds.
- Every response carries a receipt: credits charged, cache status, duration.
/v1/model/archive
{
"view": "expiring",
"withinDays": 180
}
Press Run to call the live API from your browser.
Why this exists
Built for hostile input
A Turkish address arrives as "Cd." or "Cad." or "Caddesi", with the flat number glued to the building number. Generic parsers drop half of it silently. This one tells you what it could not place.
Every number carries its provenance
Each archived point stores the source URL and a content hash of the page it came from, and the archive is committed to a Merkle root anchored in Bitcoin. Every commitment — with its cutoff, leaf count and anchors — is published at /proof, so you can check for yourself how current the latest one is. The bulletins themselves are public and anyone can read them; what this adds is that a number you quote can be shown to be the number we held on that date, and that it has not been edited since.
You only pay for work
Repeated inputs come from cache and cost zero credits. If a response ever fails its own schema, the call is refunded automatically.
Endpointsexpand any row to see the parameters and call it live
AI Infrastructure1
/v1/model/archive
LLM Price & Lifecycle Archive
1 credit
Dated archive of LLM prices, context windows, announced retirement dates and quiet delistings across 400+ models and 50+ providers.
Providers overwrite their pricing pages and drop models from their catalogs without publishing what changed. This endpoint keeps a daily record, so three otherwise unanswerable questions become answerable: what a model cost on a given date (a contract and budget question), which models were quietly removed (a dependency-audit question), and when a retirement date was first announced and whether it later moved (a migration-planning question). Price points land in the shared time series, so a full range query is available through `series/history` under `model.price.<provider>/<model>.<input|output|cache_read>`. The archive can only accumulate forward — it cannot be reconstructed after the fact.
Parameters
| view | "catalog" | "expiring" | "delisted" | "events" | "stats" | `catalog`: izlenen modeller · `expiring`: emekliliği İLAN EDİLMİŞ olanlar · `delisted`: katalogdan düşenler · `events`: yaşam döngüsü olayları · `stats`: arşivin ölçüsü. default "catalog" |
| provider | string | Sağlayıcı öneki, ör. `anthropic`, `openai`, `google`. |
| slug | string | Tam model kimliği, ör. `anthropic/claude-opus-5` (yalnız `events`). |
| q | string | Model kimliği/adında arama (yalnız `catalog`). |
| type | "listed" | "delisted" | "relisted" | "price_up" | "price_down" | "context_changed" | "expiration_announced" | "expiration_changed" | Olay türü (yalnız `events`). |
| severity | "high" | "medium" | "low" | "info" | |
| withinDays | integer | `expiring`: kaç gün içinde emekli olacaklar. default 180 |
| days | integer | `events`: kaç günlük pencere. default 90 |
| includeDelisted | boolean | `catalog`: düşmüş modelleri de listele. default false |
| limit | integer | default 100 |
/v1/model/archive
{
"view": "expiring",
"withinDays": 180
}
Press Run to call the live API from your browser.
Pricingone key covers every endpoint
Credits are consumed per call and cache hits are free. Requests without a key run on a narrow per-IP demo quota so you can evaluate before signing up.
The API key is e-mailed the moment payment clears. Upgrades keep the same key, so your integration is never broken.
Want to finish the integration before paying?
Use it from an AI assistantthe same catalogue, exposed as MCP tools
Every endpoint is also published over the Model Context Protocol, so Claude, ChatGPT or your own agent can call it directly — no glue code, no wrapper functions. The assistant sees the same input schemas and the same metering.
Currently 25 tools. New endpoints appear automatically; nothing to update on your side.
claude_desktop_config.json
{
"mcpServers": {
"temsor": {
"url": "https://api.temsor.com/mcp",
"headers": { "x-api-key": "fk_live_…" }
}
}
}
Quickstart
Official client: npm install temsor-api · npmjs.com/package/temsor-api
Node.js
import Client from "temsor-api";
const api = new Client({ apiKey: KEY });
const r = await api.${(() => {
const first = apis[0];
return first.slug.split(/[/-]/).map((p, i) => (i === 0 ? p : p[0].toUpperCase() + p.slice(1))).join('');
})()}(${esc(JSON.stringify(apis[0].examples[0]?.input ?? {}))});
console.log(r, r.$meta);cURL
curl -s https://api.temsor.com/v1/model/archive \
-H "content-type: application/json" \
-H "x-api-key: fk_live_…" \
-d '{"view":"expiring","withinDays":180}'JavaScript
const res = await fetch("https://api.temsor.com/v1/model/archive", {
method: "POST",
headers: { "content-type": "application/json", "x-api-key": KEY },
body: JSON.stringify({"view":"expiring","withinDays":180})
});
const { data } = await res.json();Python
import httpx
r = httpx.post("https://api.temsor.com/v1/model/archive",
headers={"x-api-key": KEY},
json={"view":"expiring","withinDays":180})
data = r.json()["data"]