API & MCP server

The one condition: credit

1. Show the source where the data appears. A site, app, bot message, dashboard, MCP tool or API that passes this data on names the source and links to it on the same surface: “Data: codex-reset.com”, linked to https://codex-reset.com/. A credit on a separate page does not count, and neither does “computed here” over numbers read from /api/forecast.
2. Identify server-side readers. Send a User-Agent that names the project and a way to reach it, for example myproject/1.0 (+https://myproject.example). When traffic has to be cut, anonymous readers go first.
3. Relays carry the credit with them. An API or MCP server that wraps these endpoints credits the source in its own documentation and, where the format allows, in the payload: "source": "https://codex-reset.com/".
4. Personal use needs no visible credit. A private script, a cron job that pings your own phone, a team chat alert: the identifying User-Agent is enough.

Copy this: Data: codex-reset.com

Readers that republish the data without credit, or hide who they are, are blocked at the firewall without notice. Credit restores access — write to the contact address in the footer.

MCP server

https://codex-reset.com/mcp

• Streamable HTTP, JSON-RPC 2.0, protocol 2025-06-18. POST only; a GET answers 405.
• Read-only and stateless: no session, no auth, no write tools. locale is en, zh, ja or es and changes only the human-readable copy.
• Tools read the same data as the JSON endpoints, so an agent and a browser never disagree.

Connect an agent

One line, then ask “did Codex reset today?”

Claude Code

HTTP transport, user or project scope.

claude mcp add --transport http codex-reset https://codex-reset.com/mcp

{
  "mcpServers": {
    "codex-reset": { "type": "http", "url": "https://codex-reset.com/mcp" }
  }
}

Codex

Codex CLI and the IDE extension read ~/.codex/config.toml.

[mcp_servers.codex-reset]
url = "https://codex-reset.com/mcp"

Cursor

Project file .cursor/mcp.json, or the global one under ~/.cursor.

{
  "mcpServers": {
    "codex-reset": { "url": "https://codex-reset.com/mcp" }
  }
}

Anything else

Any client that speaks streamable HTTP takes the bare URL. To check the server by hand:

curl -sS https://codex-reset.com/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

JSON API

Rules of the road

1. A reset is real when the timeline says so. The signal is an /api/timeline event with group "reset" and announcement_state "announced"; equivalently, /api/forecast last_reset_at moves forward. That is the same condition the ✅ Telegram alert fires on. A rising probability is not a reset.
2. Banked resets are a separate fact. banked_state (announced, arriving, available, unknown) never updates a reset timestamp, a count or a cadence. Treat it as supplemental.
3. Poll once a minute at most. Responses are published copies refreshed about once a minute and served with Cache-Control: max-age=60; polling faster returns the same bytes. x-published-checked-at and x-published-expires-at say how fresh a copy is. Honour Retry-After on a 429.
4. Depend only on documented fields. Paths and the fields named on this page are stable. Anything else in a payload may move or disappear without notice. Classifier internals and alert decisions are never exposed.
5. GET only. Everything documented here is a GET. The POST routes under /api/ are this site's own interface — prayers, push subscriptions, ingest — and are not part of the contract; do not build on them.

Examples

curl -sS https://codex-reset.com/api/forecast \
  -A 'myproject/1.0 (+https://myproject.example)' \
  | jq '{p24: .probabilities.rounded_24h, p48: .probabilities.rounded_48h, last: .last_reset_at}'

curl -sS https://codex-reset.com/api/timeline \
  | jq -r '[.events[] | select(.group == "reset" and .announcement_state == "announced")][0]
           | "\(.announced_at)  \(.url)"'

const res = await fetch("https://codex-reset.com/api/forecast");
const { probabilities } = await res.json();
odds.textContent = `${probabilities.rounded_24h}% in 24h`;
// next to it, in the markup:
// <small>Data: <a href="https://codex-reset.com/">codex-reset.com</a></small>

Machine-readable discovery

If all you want is to be told when a reset lands, you do not need to build anything: the Telegram and Discord channels, browser push and email alerts in the footer fire on the same signal.