Sources
Every published event links to the original source. This page describes what is monitored and how much weight each kind of source carries.
Coverage by provider
| Provider | Monitoring since | Events | Source status |
|---|---|---|---|
| CODEXOpenAI Codex | 2025-09-17 | 61 | Fresh |
| CLAUDEAnthropic Claude | 2026-04-16 | 20 | Delayed |
Monitored source registry
These are the enabled public endpoints, accounts, and policy references used by the current build. The list is generated from the same provider registry that configures detection; it is not maintained as a separate marketing list.
Provider registry 3.3.0 · detection registry 1.3.0
Codex
OpenAI Codex
| Public source | Role | Trust | How it is used |
|---|---|---|---|
| Codex changelog feed (opens in a new window)developers.openai.com/codex/changelog/rss.xml | Official announcement feed | S1 | Independent product announcements. Full feed text and original dates are reverified; generic reset instructions are not new grants. |
| OpenAI news feed (opens in a new window)openai.com/news/rss.xml | Official announcement feed | S1 | Independent product announcements. Full feed text and original dates are reverified; generic reset instructions are not new grants. |
| Codex status history RSS (opens in a new window)status.openai.com/history.rss | Official status feed | S0 | Status and incident corroboration. Each item is checked for reset relevance. |
| @thsottiaux on X (opens in a new window)x.com/thsottiaux | Announcement account | S2 | Codex product lead. Direct reset statements can become event evidence. |
| Codex pricing and limits (opens in a new window)developers.openai.com/codex/pricing | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| Codex plan help (opens in a new window)help.openai.com/en/articles/11369540-using-codex-with-your-chatgpt-plan | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| Codex changelog (opens in a new window)developers.openai.com/codex/changelog | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| Codex changelog feed (opens in a new window)developers.openai.com/codex/changelog/rss.xml | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| OpenAI news feed (opens in a new window)openai.com/news/rss.xml | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| OpenAI Status (opens in a new window)status.openai.com | Policy reference | S0 | Policy, plan, product, and affected-scope verification. |
| codex-resets.com data feed (opens in a new window)codex-resets.com/api/resets | Enumeration catalog | S3 · Reported | Allowlisted structured ID, timestamp, and reset type may publish as reported evidence. Feed prose and statistics are not copied. |
| claude-resets.com data feed (opens in a new window)claude-resets.com/data/resets.json | Enumeration catalog | Discovery only | Candidate enumeration only. Original evidence is checked before publication. |
Claude
Anthropic Claude
| Public source | Role | Trust | How it is used |
|---|---|---|---|
| Claude status history RSS (opens in a new window)status.claude.com/history.rss | Official status feed | S0 | Status and incident corroboration. Each item is checked for reset relevance. |
| @ClaudeDevs on X (opens in a new window)x.com/ClaudeDevs | Announcement account | S1 | Anthropic official developer account. Direct reset statements can become event evidence. |
| @lydiahallie on X (opens in a new window)x.com/lydiahallie | Announcement account | S2 | Claude Code staff. Direct reset statements can become event evidence. |
| Understanding usage and length limits (opens in a new window)support.anthropic.com/en/articles/11647753-understanding-usage-and-length-limits | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| Usage limit best practices (opens in a new window)support.anthropic.com/en/articles/9797557-usage-limit-best-practices | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| Claude Code plan usage (opens in a new window)support.anthropic.com/en/articles/11145838-using-claude-code-with-your-pro-or-max-plan | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| Anthropic Status (opens in a new window)status.claude.com | Policy reference | S0 | Policy, plan, product, and affected-scope verification. |
| Anthropic news (opens in a new window)www.anthropic.com/news | Policy reference | S1 | Policy, plan, product, and affected-scope verification. |
| claude-resets.com data feed (opens in a new window)claude-resets.com/data/resets.json | Enumeration catalog | Discovery only | Candidate enumeration only. Original evidence is checked before publication. |
From detection to publication
- Enumerate. Enabled accounts, feeds, and catalogs are checked every 10 minutes.
- Verify. Deterministic rules evaluate the original statement, identity, timing, and affected scope.
- Publish or reject. Only qualifying evidence enters the public ledger; rejected candidates do not become events.
An allowlisted catalog fact can publish only as Reported and is excluded from verified-only interval statistics. Other catalogs remain discovery-only. Event pages preserve the public link supporting each record.
Source trust levels
- S0
- Official machine-readable status or API.
- S1
- Official documentation, help centre, changelog, or an official company account.
- S2
- An approved staff account making a direct statement about their own product.
- S3
- Credible secondary reporting. Requires corroboration.
- S4
- Community reports. Supporting evidence only, never sufficient to publish.
What we do not do
- We do not ask for, store, or transmit your provider account credentials.
- We do not bypass logins, CAPTCHAs, or access restrictions.
- We do not republish source content in full. We link to the original.
- When a source is removed, we stop showing the quotation and re-evaluate the event's confidence rather than silently keeping the claim.
When sources go quiet
If monitoring is interrupted, the affected provider is marked as delayed or stale and the last successful check is shown. Stored history stays available. We never present "no reset happened" as a fresh conclusion during an outage.