Gemini Reset TimeAntigravity public resets History 中文 Alerts

Data

Developer access to reset data

The same records that power this site, in formats you can script against. Free, read-only, no key.

Endpoints

Endpoint Format Contents
https://updates.geminiresettime.com/ledger.json JSON The published ledger
https://updates.geminiresettime.com/feed.xml Atom 1.0, application/atom+xml One entry per record, newest first
https://updates.geminiresettime.com/resets.ics iCalendar Public confirmation times and future official times or windows
https://updates.geminiresettime.com/status.json JSON Latest confirmed reset, archive dates and frequency reference
https://updates.geminiresettime.com/api/mcp MCP over HTTP Read-only tools status and list_records

The data endpoints read the same published ledger.

Agent Skill

Get the Gemini Reset Time Skill. It gives an agent the public status and ledger URLs, with steps for checking timestamps and original announcements.

JSON shape

The public JSON response contains the ledger directly. historicalGapReference gives the same recorded gap counts as the Reset frequency page.

{
  "checkedAt": "2026-11-21T17:07:55Z",
  "coverageFrom": "2026-05-21T05:25:12Z",
  "entries": [
    {
      "id": "2124070033534161407",
      "eventId": "neon-cache",
      "type": "confirmed",
      "at": "2026-11-21T09:18:53Z",
      "title": "Gemini quota reset after the Neon cache update",
      "scope": "Gemini · all Antigravity users",
      "summary": "…",
      "source": "https://x.com/_mohansolo/status/2124070033534161407",
      "corroboration": "https://resetnow.ai/events/2026-11-21-antigravity-gemini-quota-reset/"
    }
  ],
  "historicalGapReference": {
    "recordedGaps": 12,
    "horizons": [
      {
        "hours": 24,
        "hits": 2,
        "gaps": 12,
        "value": 0.16666666666666666
      }
    ]
  }
}

Fields

  • checkedAt: when an editor last reviewed sources, in UTC.
  • coverageFrom: the first post in the archive. The archive was assembled from public posts and archives, so it has recorded gaps rather than continuous coverage.
  • id: the ID of the source post on X.
  • type: confirmed (the team says the reset happened), signal (a teaser or hint), scheduled (an official time or window in scheduledStart and optional scheduledEnd), rollout (the team says it has started).
  • eventId: groups records about the same reset. Count each event once.
  • at: when the post was published, in UTC. Not when anyone's quota changed.
  • source: the original post. corroboration, when present, is a public archive page or a second post used to verify it.
  • countInBaseline: present and false when a confirmation stays in the archive but is left out of the reset frequency, for example because the post didn't name a model scope.

Example: latest confirmed reset

const res = await fetch("https://updates.geminiresettime.com/ledger.json");
const body = await res.json();
const data = body.value ?? body;
const firstConfirm = new Map();
for (const e of data.entries) {
  if (e.type !== "confirmed") continue;
  const prev = firstConfirm.get(e.eventId);
  if (!prev || Date.parse(e.at) < Date.parse(prev.at)) firstConfirm.set(e.eventId, e);
}
const latest = [...firstConfirm.values()].sort((a, b) => Date.parse(b.at) - Date.parse(a.at))[0];
console.log(latest ? `${latest.at} ${latest.scope}` : "none recorded");

MCP

Add the endpoint to an MCP client that supports remote HTTP servers:

{
  "mcpServers": {
    "gemini-reset-time": { "url": "https://updates.geminiresettime.com/api/mcp" }
  }
}

status returns the latest confirmation, archive dates and the recorded gap reference. list_records returns ledger records. Both are read-only; tools/list gives the exact input schema. A manual check from a terminal:

curl -s https://updates.geminiresettime.com/api/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -H 'mcp-protocol-version: 2025-11-25' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Fair use

  • Poll at most every 15 minutes. Data only changes when an editor publishes.
  • Show the record's source link wherever you display a record.
  • The JSON endpoint accepts cross-origin browser reads.
  • No key and no uptime promise. Format changes will be noted on this page.

Related

Last reviewed 21 Nov 2026