Answer: latestN continuously collects the current state of fast-changing facts from official sources, and publishes each one with its sources, timestamps and verification record. Entries: 85 Sources cited: 84 Confirmed: 82 Not yet published: 0 Check failed: 3 Overdue: 0 No longer tracked: 0 Newest change: 2026-11-12T10:44:42Z Most recent verification: 2026-11-12T10:44:43Z Latest changes: https://latestn.com/latest Generated: 2026-11-12T10:56:08Z Why this exists: Many facts an agent needs go stale. Which model IDs still work and what they cost. Which version of a package is current and when the old one stops getting fixes. When a public holiday falls this year. Which rate applies this month. Checking any one of them means finding the official page, reading it, and making sure it has not changed. Every agent that needs the fact repeats that work. We do that work once, continuously, and publish the result. We keep collecting the current state of these facts from official sources around the world, re-check every entry on a published schedule, and record every change. Each entry carries what is needed to judge it without redoing the research: the sources it rests on, the exact passage quoted from each, when each source was accessed, how the value was verified, when it last changed, and when it will be checked next. Where something is not yet known, or a check has failed, the entry says so. Our aim is to save other agents work: one clean, simple place to look up a current fact, with everything needed to decide whether to rely on it. What we cover: Category | Covers | Entries | Checked | Primary sources | Example https://latestn.com/model/ | AI models: current model IDs, pricing, context length, deprecation status and successors | 5 | Daily | Official model, pricing and deprecation pages of each provider | https://latestn.com/model/deepseek https://latestn.com/version/ | Software versions: current stable releases, support status and end-of-life dates | 21 | Daily | Official release pages, release feeds and package registries | https://latestn.com/version/python https://latestn.com/device/ | Devices: the latest phones, computers, consoles, chips and cars | 11 | Daily | Manufacturers' official product pages | https://latestn.com/device/iphone https://latestn.com/people/ | Who currently holds major offices | 5 | Weekly | Official government and institution websites | https://latestn.com/people/us-president https://latestn.com/sports/ | The latest champions of major competitions | 1 | Weekly | Official league and tournament websites | — https://latestn.com/awards/ | The latest winners of major awards | 2 | Weekly | Official award websites | — https://latestn.com/finance/ | Official rates and figures: interest rates, inflation, wages, postage | 8 | Daily | Central banks, statistics agencies and government departments | https://latestn.com/finance/fed-funds-rate https://latestn.com/tax/ | Tax brackets, deductions and contribution limits | 4 | Daily | Internal Revenue Service | https://latestn.com/tax/401k-limit https://latestn.com/subscription/ | Current prices of popular subscriptions | 3 | Daily | Official pricing pages | https://latestn.com/subscription/netflix https://latestn.com/travel/ | Travel rules, fees and processing times | 1 | Daily | Government travel and border agencies | https://latestn.com/travel/tsa-liquids https://latestn.com/health/ | Official health notices, approvals and code sets | 4 | Daily | CDC, FDA, CMS and WHO | https://latestn.com/health/fda-novel-drugs https://latestn.com/science/ | Scientific reference data, catalogs and records | 14 | Daily or weekly | NASA, NOAA, NIST, NCBI, EMBL-EBI and other scientific bodies | https://latestn.com/science/exoplanets https://latestn.com/standards/ | The latest versions of technical standards | 6 | Weekly | Standards bodies and industry consortia | https://latestn.com/standards/unicode And more. Coverage grows continuously. If a fact you need is not listed, request the URL where you would expect to find it, for example /model/{model-id} or /version/{software}. Every unmatched request is logged, and those requests decide what we add next. What we do not cover: Personal data of any kind. No tool here takes personal information as input. Opinions, rankings, forecasts and advice. Anything without an official source we can quote. What every entry contains: Answer: The fact in one sentence, with numbers and units. Always the first line of the page. Status: Confirmed: verified against the primary source at the last check. Not yet published: the authority has not released it; no value is given. Check failed: the last check could not reach or read the source; the value shown is from the last successful check, and the time of the failed attempt is shown. No longer tracked: we stopped checking this entry; it is kept for reference, may be out of date, and is not offered to search engines. Overdue: the scheduled check has not succeeded within 6 hours of its due time; set automatically. Entry, revision, digest: The entry ID is its URL path and never changes. The revision number goes up by one each time the content changes. The digest is a hash of the current content: if it matches what you saw before, nothing has changed. Valid: The period the value applies to, where that matters, such as a contribution year or a rate period. This is separate from when we checked it. Timeline: Created: when we started tracking the entry. Last changed: when the value itself last changed. Last verified: when we last confirmed it against the source. Next check: when we will check again. Check interval: how often we check. Expected change: when the authority usually updates it. All times are ISO 8601 in UTC. Data: Every value in a table, with its unit, the numbered source it comes from, and the date it holds for. Previous: Every earlier answer and the period during which it was the latest, with its source. Sources: Numbered references. Each gives the publisher, the document title, the URL, when we accessed it, the exact quoted passage, where in the document the passage is, whether it is a primary (official) or secondary source, and, where available, a SHA-256 hash of the document as fetched and an archived copy. Verification: How the value was obtained and checked: the extraction method, the cross-check against an independent source and its result, and the time of the last successful check. Notes and limitations: What the value covers and does not cover, and known caveats. Change log: Every change since the entry was created, with old and new values and the source behind each change. Challenge this entry: How many challenges are open, and how to send one: what is wrong and a link to evidence. Agents can submit with a single GET or POST request. How to cite: A citation line and a BibTeX entry pinned to the current revision and digest. Example: the top of an entry: Answer: The latest Grammy for Album of the Year was won by Bad Bunny, at the 68th Annual Grammy Awards in 2026. Status: Confirmed Entry: awards/grammy-album Revision: 1 Digest: sha256:b44b72a3022974bd (changes whenever the content changes) Timeline: Created: 2026-11-12T10:44:33Z Last changed: 2026-11-12T10:44:33Z Last verified: 2026-11-12T10:44:33Z Next check: 2026-11-19T10:44:33Z Check interval: Weekly Expected change: No fixed schedule Full entry: https://latestn.com/awards/grammy-album How entries are verified: 1. Every entry starts from a named official source: the provider, project or government body that publishes the fact. Without one, the entry is not published. 2. We fetch the source and extract the value, and store the exact supporting passage as a quote together with its location in the document. 3. We check every quoted passage against the fetched document by code: each quote must appear in it word for word, and each value must appear in its quote. Values that fail are not published. 4. Where an independent second source exists, the value is cross-checked against it. If the two disagree, the change is held and not published until resolved. 5. Every entry is re-checked on its schedule. When the value changes, the entry is updated, its revision goes up, and the change is written to its change log with the old value, the new value and the source. 6. When a check fails, the entry says so. Last verified stays at the last successful check, the failed attempt is shown, and the status becomes Check failed. When a check is late, the status becomes Overdue automatically. An old value is never presented as a current one. How to find what you need: Guess the URL: Paths follow /{category}/{id}. IDs are lowercase with hyphens and use the official identifier where one exists: the API model ID, the package name, the ISO country code. Common alternate names, spellings and capitalisations redirect to the canonical URL, so a reasonable guess usually works. Browse: Each category has an index at /{category}/ listing every entry with its answer, status and last verification time. The index alone often answers the question. Search: Use /q/{keywords}. Separate words with a space or +; every word must match. A unique match returns the entry itself. Otherwise you get a list of matching entries. See what changed: Use /latest/{n}, or narrow it to a category, a keyword or a single entry by putting that in front: /model/latest/20, /q/deepseek/latest/5, /model/deepseek-chat/latest. Each line has the time, the kind of change, the entry URL and the old and new values. Stay in sync: Use /latest?since={ISO time} with the newest time you saw last. Long results end with an Older link; follow it to continue. An Atom feed is at /latest.xml. When nothing matches: You get a 404 page with the closest entries and the category indexes. The request is logged, and unmet requests decide what we cover next. Report an error: Every entry has a Challenge this entry section. Send what is wrong and a link to evidence to /dispute/{entry}, by POST or by GET with ?claim=...&evidence_url=... . Challenges are queued and checked against the evidence, and open challenges are counted on the entry page. Formats: Plain text by default, HTML if the request accepts text/html. The content is the same in both. URL patterns: current state: https://latestn.com/model/{model-id} LLM model ID, pricing, context length, deprecation status, successor https://latestn.com/version/{software} Current stable release and end-of-life dates https://latestn.com/deprecated/{name} Deprecated or renamed APIs, models and SDKs, and their replacements https://latestn.com/holiday/{country}/{year} Public holidays and make-up workdays (country: cn) https://latestn.com/shebao/{city}/{year} China social insurance contribution bases https://latestn.com/tax/{name} China individual income tax rules and LPR https://latestn.com/{category}/ Every entry in a category URL patterns: latest changes: https://latestn.com/latest/{n} Most recent n changes across the site (default 10, max 100) https://latestn.com/{category}/latest/{n} Most recent changes in one category https://latestn.com/q/{keywords}/latest/{n} Most recent changes to entries matching keywords https://latestn.com/{entry}/latest/{n} Change history of one entry https://latestn.com/latest?since={ISO time} Every change after a point in time https://latestn.com/latest.xml Atom feed URL patterns: search and computed answers: https://latestn.com/q/{keywords} Search. A unique match returns the entry itself https://latestn.com/now?tz={IANA zone} Current date, time and weekday (UTC by default) https://latestn.com/workday/{country}/{YYYY-MM-DD} Whether a date is a working day Citing: Cite the entry, not the site. Every entry ends with a citation line and a BibTeX entry pinned to its current revision and digest, so a citation always points to the exact content that was read. URL: https://latestn.com/