Score global de préparation IA
Résultat combiné de tous les signaux de l’audit.
Score global de préparation IA
Résultat combiné de tous les signaux de l’audit.
Évaluation globale de préparation IA
claude-resets.com (claude-resets.com) a obtenu 74/100 lors de l’audit technique automatisé de préparation à l’IA. llms.txt était accessible, llms-full.txt avait aucun fichier accessible et ai.txt était introuvable. L’analyse de robots.txt a trouvé 6 robots IA explicitement autorisés, 5 bloqués et 1 sitemap déclaré. La complétude du balisage de la page d’accueil atteint 100% ; types Schema.org détectés : WebSite, WebPage, Dataset, FAQPage. Balises OpenGraph détectées : 11. Les résultats correspondent aux réponses publiques observées le 2026-11-12T08:41:44.151Z.
L’audit combine les fichiers lisibles par les machines, les règles des robots, les sitemaps et le balisage de la page d’accueil. llms.txt est accessible et contient 1 377 jetons.
robots.txt est disponible ; robots IA bloqués : 5. Sitemaps déclarés : 1. Types Schema.org : WebSite, WebPage, Dataset.
Le profil Lighthouse mobile est encore en cours de collecte.
La file d’attente collecte les performances mobiles, l’accessibilité, les bonnes pratiques, le SEO et les signaux expérimentaux pour agents de navigateur.
Fichiers lisibles par les machines, règles des robots, découverte et balisage de la page d’accueil.
La version complète est introuvable
Le fichier ai.txt est introuvable
1 sitemap trouvé
Types : WebSite, WebPage, Dataset, FAQPage
11 balises OpenGraph trouvées
D’après l’analyse de robots.txt
Parcours de découverte déclarés pour les robots et les agents.
Métadonnées d’aperçu social détectées sur la page d’accueil.
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:height630Entités et propriétés structurées exposées sur la page d’accueil.
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/
Des sites au score de préparation IA proche — comparez leur llms.txt et leur balisage.