Events
The market log as data. Curated and detected rows merged, newest first.
GET /api/v1/eventscurl "https://vitna.ai/api/v1/events?kind=price&since=2026-01-01"Query parameters
| Parameter | Values | Meaning |
|---|---|---|
kind | launch, price, policy, deprecation, availability | One kind |
origin | curated, detected | Who wrote it |
since | YYYY-MM-DD | On or after this day |
All optional, and combinable.
Response
{
"events": [
{
"date": "2026-08-22",
"provider": "Anthropic",
"kind": "price",
"origin": "detected",
"title": "...",
"detail": "...",
"sourceUrl": "https://...",
"evidence": [ { "label": "before", "sha256": "..." }, { "label": "after", "sha256": "..." } ],
"supersedes": null,
"supersededBy": null
}
],
"meta": { "generatedAt": "...", "source": "database", "count": 12, "retrieved": "2026-08-23" }
}date is a day, not an instant
An event records the day something happened. The read that confirmed it is on the observation, not here.
evidence on detected rows
A detected price move carries the hashes of both archived documents, before and after. That is what makes the move checkable rather than merely stated: fetch both, compare, and see the change yourself.
supersedes and supersededBy
The log is append-only, so a row that was wrong is corrected by a new row and never edited. The correction carries supersedes, naming the row it restates as <date> <title>, and that row carries supersededBy, naming the correction back. Both are null on a row that is neither.
A correction keeps the date of the row it restates and says the true date in its text where the two differ. It may restate a detected row: a move read from a figure that was misread, or right about the price and wrong about the day. Read a row with a supersededBy as what the record said, not what it says.
Errors
| Status | Code | Cause |
|---|---|---|
| 404 | unknown_kind | Not one of the five kinds |
| 400 | bad_since | Not an ISO date. The message shows the expected form. |
An unknown origin is not rejected; it simply matches nothing.
Same source as the page
This reads the same loaded snapshot the /log page renders, so the page and the API cannot drift.
Caching
public, max-age=60, stale-while-revalidate=3600.
