Gesamtwert der KI-Bereitschaft
Zusammengefasster Wert aus allen Auditsignalen.
Gesamtwert der KI-Bereitschaft
Zusammengefasster Wert aus allen Auditsignalen.
Gesamtbewertung der KI-Bereitschaft
claude-resets.com (claude-resets.com) erreichte im automatisierten technischen Audit 74/100 Punkte bei der KI-Bereitschaft. llms.txt war erreichbar, llms-full.txt hatte keine erreichbare Datei und ai.txt war nicht auffindbar. Die robots.txt-Analyse ergab 6 ausdrücklich erlaubte und 5 blockierte KI-Crawler sowie 1 deklarierte Sitemap. Die Vollständigkeit des Homepage-Markups lag bei 100%; erkannte Schema.org-Typen: WebSite, WebPage, Dataset, FAQPage. Erkannte OpenGraph-Tags: 11. Die Ergebnisse entsprechen den öffentlich erreichbaren Antworten der Website zum Prüfzeitpunkt 2026-11-12T08:41:44.151Z.
Die Prüfung kombiniert maschinenlesbare Dateien, Crawler-Regeln, Sitemaps und Homepage-Markup. llms.txt ist erreichbar und umfasst 1.377 Tokens.
robots.txt ist verfügbar; blockierte KI-Bots: 5. Deklarierte Sitemaps: 1. Schema.org-Typen: WebSite, WebPage, Dataset.
Das mobile Lighthouse-Profil wird noch erfasst.
Die Hintergrundwarteschlange erfasst mobile Performance, Barrierefreiheit, Best Practices, SEO und experimentelle Signale für Browser-Agenten.
Maschinenlesbare Dateien, Crawler-Regeln, Discovery und Homepage-Markup.
Vollständige Version wurde nicht gefunden
ai.txt wurde nicht gefunden
1 Sitemap gefunden
Typen: WebSite, WebPage, Dataset, FAQPage
11 OpenGraph-Tags gefunden
Basierend auf der robots.txt-Analyse
Deklarierte Discovery-Routen für Crawler und Agenten.
Auf der Startseite gefundene Metadaten für Social-Media-Vorschauen.
og:typewebsiteog:site_nameclaude-resets.comog:localeen_USog:titleClaude Usage Reset Tracker: Days Since the Last Claude Resetog:descriptionClaude reset tracker: the last announced Claude Code banked reset was Nov 10, 2026 (Pro, Max, Ultra + Team). Every Claude usage reset, with sources and alerts.og:image:altclaude-resets.com: Claude Code usage limits were last reset on Nov 10, 2026. Banked reset · Pro, Max, Ultra + Team.og:urlhttps://claude-resets.com/?lang=enog:image:typeimage/pngog:image:width1200og:image:height630Strukturierte Entitäten und Eigenschaften der Startseite.
nameclaude-resets.comurlhttps://claude-resets.com/descriptionClaude reset tracker: how long since Anthropic last reset Claude Code's usage limits, with the full announcement archive and a head-to-head against OpenAI Codex.alternateNameClaude Reset Tracker, Claude Usage Reset TrackerinLanguageendateModified2026-11-11# claude-resets.com
> Claude reset tracker: Claude Code usage-limit resets announced by @ClaudeDevs and Claude Code team members, with a head-to-head against OpenAI Codex resets.
This site answers: "How long since the last Claude reset?" and "When has Anthropic reset Claude Code limits?"
## Primary pages
- Homepage: https://claude-resets.com/
- Monthly Claude vs Codex report: https://claude-resets.com/claude-vs-codex/
- Monthly counts (CSV): https://claude-resets.com/data/monthly-resets.csv
- Machine summary (JSON): https://claude-resets.com/data/summary.json
- Live catalog (JSON): https://claude-resets.com/api/resets
- Full dataset (JSON): https://claude-resets.com/data/resets.json
- Reset-only RSS: https://claude-resets.com/rss/resets.xml
- All-announcements RSS: https://claude-resets.com/rss.xml
- Reset calendar (iCalendar): https://claude-resets.com/calendar.ics (`?provider=codex` or `?provider=all`)
- MCP server (Streamable HTTP, read-only): https://claude-resets.com/mcp — `claude mcp add --transport http claude-resets https://claude-resets.com/mcp`
- Claude Code status line script: https://claude-resets.com/statusline.sh (reads https://claude-resets.com/api/statusline)
- This file: https://claude-resets.com/llms.txt
## Snapshot
- Last Claude reset: 2026-11-10T21:59:58Z (https://x.com/ClaudeDevs/status/2120275296637321476)
- Claude resets tracked: 16 (banked: 3)
- Claude limit changes tracked (not counted as resets): 6
- Mean gap between Claude resets: 13.9 days
- Longest Claude drought: 48.1 days
- Codex resets tracked: 59
## Dataset contract
`/data/resets.json` shape:
```
{
"providers": {
"claude|codex": {
"name", "product", "account", "accountUrl",
"events": [
{ "id", "date", "kind", "resetType?", "usableUntil?", "account?", "scope?", "note?", "url?" }
]
}
}
}
```
Field meanings:
- `kind: "reset"` — counters were flushed; counts toward every metric
- `kind: "policy"` — ceiling moved, nothing flushed; archive only
- `resetType: "banked"` — a reset users apply themselves when they choose instead of an immediate flush; still `kind: "reset"` and counted, the same way codex-resets.com counts them. Absent means a regular reset.
- `usableUntil` — banked resets only, when the announcement set a deadline: the last moment it can be applied, as a UTC ISO timestamp (a stated day runs to 23:59:59 UTC)
- `date` — UTC ISO timestamp decoded from the X status ID snowflake (not transcribed). A reset recorded from an announcement page keeps the time it was given, and the few Codex resets codex-resets.com observed rather than took from a post keep the time it reports.
- `account` — source X account when it differs from the provider's primary account
- `scope` — who was affected when known
- `note` — summary of the announcement; entries the service added automatically keep the post's own text until edited (a quote post gets the site's stock sentence). Verify against `url`
`/data/summary.json` is the short form of the Claude side only. It intentionally omits "days since last reset" so the file stays stable between rebuilds; compute that from `lastResetAt` and the current UTC time. Its `bankedResets` lists every banked announcement's `id`, `date`, `scope`, `usableUntil` (or null) and `url`: compare each deadline with your own clock. It is announcement history, not an individual user's unused reset balance. The hero and MCP list all unexpired known deadlines, and the status line shows their count and next expiry.
`/api/resets` returns the same provider catalog plus runtime metadata. Catalogued
events have `verification: "curated"`. A Claude reset or limit change the service
has detected but not yet added to the catalog has `verification: "provisional"`. Codex resets that codex-resets.com lists but this
catalog does not include yet have `verification: "upstream"`; the few it observed
rather than took from a post keep the time it reports instead of a decoded one.
Codex resets found in @thsottiaux's posts while codex-resets.com is unavailable are
`"provisional"`. `meta.detector.status` and `meta.codexSync.status` say whether
live detection is working (`fresh`) or `starting`, `offline` (not polling), `degraded` or `stale`, and
`meta.provisionalEventIds` lists provisional Claude resets. A provisional banked
reset's `usableUntil` was read from the post and may still be corrected.
## Scope
Claude subscription usage-limit announcements from @ClaudeDevs and Claude Code team members are tracked. Coverage begins with @ClaudeDevs's first reset announcement; earlier Anthropic resets are out of scope, not missing. Codex history comes from https://codex-resets.com/; dates in `/data/resets.json` are decoded from each post's status ID, except the few Codex resets codex-resets.com observed rather than took from a post, which keep the time it reports. A reset recorded from an announcement page keeps the time it was given and links that page when one was given. It is included even when codex-resets.com has not listed it, so this count can differ from that dataset. The same announcement still counts once.
## License
The catalog, summaries and monthly counts are licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/): reuse them freely with credit to claude-resets.com. Text quoted from a post belongs to its author, and Codex rows come from https://codex-resets.com/.
## Optional
- Sitemap: https://claude-resets.com/sitemap.xml
- Codex comparison site: https://codex-resets.com/
Websites mit ähnlicher KI-Bereitschaft — vergleichen Sie llms.txt und Markup.