Codex reset API & MCP server

Endpoints

• GET https://codexreset.ai/api/v1/resets.json — every recorded reset event, including a top-level attribution object and a per-event seeded flag (see below).
• GET https://codexreset.ai/api/v1/forecast.json — a relay of whenreset.app's own live 24h/48h/7d probabilities, backtest, and model info (see below — this site's own forecast engine is research-only and is never served here).
• GET https://codexreset.ai/api/v1/signals.json — the three live signal inputs on their own.
• GET https://codexreset.ai/api/v1/status.json — the Codex-related OpenAI status snapshot.
• GET https://codexreset.ai/feed.xml — Atom feed, latest 50 recorded resets.
• GET https://codexreset.ai/resets.ics — recorded resets as an all-day calendar.
• POST https://codexreset.ai/mcp — MCP server (JSON-RPC 2.0, Streamable HTTP).

Every endpoint is CORS-enabled (Access-Control-Allow-Origin: *), cached 5 minutes at the edge, and X-Robots-Tag: noindex (the JSON itself isn't meant to be indexed; this page is).

Example: curl

curl -s https://codexreset.ai/api/v1/resets.json | jq '.events[0]'

Example: JavaScript fetch

const r = await fetch("https://codexreset.ai/api/v1/forecast.json").then(r => r.json());
console.log(`24h: ${r.probabilities.raw_24h}, 48h: ${r.probabilities.raw_48h}, model: ${r.model}`);

Reset odds: whenreset.app is the single source

/api/v1/forecast.json and the get_forecast MCP tool are both a live relay of whenreset.app's own forecast API — the shared source this site and its sibling trackers (agentresets.com, claudereset.org, howtok.net) all now display, instead of each running its own model and disagreeing. If whenreset.app can't be reached, both return "available": false rather than falling back to a locally computed number. This site's own cadence-engine backtest is kept for research only (documented at /forecast-method/) and is never included in any API response.

/api/v1/resets.json — delivery fields

Each event carries when it was announced and, separately, when it was actually delivered to accounts — these are often not the same moment (a reset can be announced and then roll out in batches over several hours).

/api/v1/resets.json — scheduled field

A top-level scheduled object appears when an official reset has been announced or hinted but hasn't landed yet — null the rest of the time (which is most of the time). It disappears again once a matching reset event is recorded, or if the announcement itself is withdrawn.

This is what the announcement post itself says, not a schedule this site vouches for — see the footer disclaimer.

/api/v1/resets.json — sample

Generated Nov 8, 2026 08:56 UTC.

{
  "schema_version": 1,
  "generated_at": "2026-11-08T08:56:46Z",
  "source": "https://codexreset.ai",
  "attribution": {
    "seed_archive": "https://codex-resets.com/",
    "note": "Reset history before 2026-09-10 was seeded from the public archive at https://codex-resets.com/."
  },
  "events": [
    {
      "id": "2117035794678546764",
      "date": "2026-11-01",
      "ts": "2026-11-01T23:27:20Z",
      "kind": "banked",
      "scope": "all",
      "summary": "Day 28/ Banked 2/2",
      "summary_unavailable": false,
      "url": "https://x.com/thsottiaux/status/2117035794678546764",
      "seeded": false,
      "announced_at": "2026-11-01T23:27:20Z",
      "delivered_at": null,
      "delivered_source_url": null,
      "delivery_reported_delay": false,
      "delivery_note_en": null
    }
  ],
  "scheduled": null
}

MCP server

A read-only Model Context Protocol server at https://codexreset.ai/mcp — stateless JSON-RPC 2.0 over plain HTTP POST, no API key, no session, no write operations.

claude mcp add --transport http codexreset https://codexreset.ai/mcp

Data sources

• Recorded reset events: public posts about Codex, checked periodically, each with a source link when available.
• Reset history before 2026-09-10: seeded from the public archive at codex-resets.com — every such event has "seeded": true in /api/v1/resets.json, and the payload's own top-level attribution object names the source.
• OpenAI's own status feed for Codex-related components.
• GitHub issue activity on openai/codex.

Attribution & fair use

Free to use, no key required. Attribution appreciated — link back to codexreset.ai if you build something with this. Please cache client-side and stay under roughly 1 request per minute. If you republish pre-2026-09-10 history, please keep the seeded/attribution fields intact and link codex-resets.com the same way this site does.