For developers
The Parallax API
Two read-only endpoints. One returns every verdict this publication has published, with the dated tells that will settle it. The other returns metadata for the published pieces. Both need a token, and a token is free.
What it is for
The ledger is the part of Parallax worth reading against something else. It records what was called, when, how confident the call was, and what has happened since, including the calls that turned out wrong. That is a dataset, and it is more useful to a researcher inside their own tools than inside our page.
Article text is deliberately not available. A piece served from somewhere else loses its sources, its figures and its corrections, and the corrections matter most: a verdict that gets updated here stays wrong in a copy. Every response links to the piece instead.
The endpoints
GET /api/v1/ledger
Scope: ledger:read
Every published verdict. Each entry carries the claim quoted verbatim with its source and date, the verdict, the confidence, the current status, the observables with their dates, and a link to the article.
GET /api/v1/articles
Scope: articles:read
Published pieces: title, link, topic, series, publication date, and the claim where the piece examines one. No article text.
curl -H "Authorization: Bearer plx_..." \
https://parallax.industries/api/v1/ledgerJSON, published rows only. Responses may be cached for five minutes. Sixty requests a minute per token; over that the answer is 429 with a Retry-After header saying how long to wait.
Attribution
Anything published from this data credits Parallax and links to the piece the row came from. Every entry carries the attribution line it should be published with, so the requirement travels with the row rather than living only here.
The ledger includes calls that were wrong. Reproducing the hits without them misrepresents the record, which is the one use of this data we would ask you not to make.
Requesting a token
Tokens are issued by hand at the moment. Write to editor@parallax.industries and say what you are building and which endpoints you need. There is no charge.
A token is shown once, when it is issued, and cannot be recovered afterwards. Only a hash of it is stored here. If one is lost or exposed, say so and it will be revoked and replaced.
If you only want new pieces
There is an RSS feed. It needs no token and no signup, and a reader checks it for you. The API is for working with the ledger as data; the feed is for being told when there is something new.