Dated changes to the API and to these documents. A change to what the API returns is listed here before, or when, it reaches the service. Current facts version: 2026-11-13.1.
These pages no longer say “geopolitical markets first”. First-pass matching runs across politics, geopolitics, economics and finance, technology, commodities and science contracts, and the closer reading is reserved for the most actively traded. Sports, crypto and entertainment markets are not covered yet. Coverage is intended to expand; no date is committed.
The home page is shorter. The full field list, the four coverage states and the selection details now live in the API docs and How it works.
Documentation only. The API, its responses and facts version 2026-11-13.1 are unchanged, and the coverage endpoint still reports declared scope and screening status as not supplied.
Facts version 2026-11-13.1 pins the published
client 0.3.0.
It adds whoami, doctor, audit
and disconnect, recoverable key creation and private
pending-operation park/resume. An unknown disconnect reply preserves
local material; expiry alone never proves linked keys were revoked.
The matching backend is already installed. No new scope, billing authority, dependency or package-registry release is added.
Facts version 2026-11-12.1 documents hosted source
d8d2f2c, installed and checked. Public routes,
authentication boundaries and existing noncharged account usage passed.
Real browser approval and paid checkout flows require their own tests.
The release adds GET and
DELETE /account/v1/connection, so a connected program can
read its own connection and disconnect itself with its keys;
GET /account/v1/audit, a bounded history of successful
access changes; and a form of POST /account/v1/keys for
connected programs that can be repeated safely after a lost reply, with
the new error key_creation_conflict (409). No permission
is added and nothing renews without a person's approval. The
reference has the details.
The home page, terms and this reference state that sign-in is with Google or GitHub.
Hosted source f776f0a, facts version 2026-11-11.1, documents the account activation summary
and each key’s most recent successful news request. The account page
shows recent success; records for older accounts explicitly cover the
period since recording began. No earlier first-call time is invented,
and no request content or per-request history is stored.
The homepage and account page now have a “Copy setup prompt” button. It copies public setup instructions and contains no credential.
Facts version 2026-11-10.8. The terms and privacy notice are published and name the operator, Michael O'Rourke. They state plainly that he also trades on Polymarket and that his trading system processes news matches before API customers receive them; no interval has been measured and not every match leads to a trade.
Documentation corrections. Coverage responses
carry the X-RateLimit headers of the news allowance, not
of the separate coverage allowance. The pinned client now sends
throughline start-from-now through the same bounded
request path as its other commands, and its denial message reads
"No keys from this request are active."
The hosted service runs release 1641146. Live
route checks verified account links, the new usage endpoint, and
creation of a pairing request. The installed limits are listed
in the API reference.
Pairing. A program can ask for access with
POST /auth/v1/pairings and collect the result with
POST /auth/v1/token. One signed-in person approves or
denies it in the account page and chooses the permissions. The program
generates its own key and sends only a hash during registration.
The approval receipt contains key and connection metadata. The throughline command in the public
client repository does this. See
Connecting a program.
Connections. The account page lists approved connections and can revoke one, which revokes every key it holds. Scoped management credentials can read the account, list keys, create and revoke keys, and read billing state, only as far as the person allowed. Payment, the trial and approval stay in the browser.
Usage. GET /v1/usage returns the plan
and the current usage without spending a news response.
Errors. Error bodies keep error and
add message, docs_url and
request_id; every response carries
X-Request-ID. Quota errors add upgrade_url and
reset_at. On feed routes 401 is now
missing_or_malformed_key or invalid_key
instead of unauthorized; clients that branch on the status
are unaffected. A market filter that is not a condition ID is
400 invalid_market_id. Clients must ignore fields they do
not know.
Pages. Added a contact page and working drafts of terms and a privacy notice. The drafts are not in force and list what is not yet decided.
Facts version 2026-11-10.4 describes the foundation release of the
service (source 31c4386). These documents are published
after that release is running; they are derived from the source and are
not yet audited against the running server.
cursor=latest on the news routes returns an empty page
whose next_cursor is the current head of the whole feed.
Save the number and poll with it; do not repeat latest. The
capture counts as one news response. Replay from zero is unchanged. See
Reading forward.
GET /account/v1/keys?order=newest lists keys newest
first and ends with a null next_cursor. Without
order, the listing behaves as before.
GET / on the API host returns public pointers to the
account page and these documents. GET /account/, and
/account with a query string, redirect to the fixed
/account. Unknown paths still get an empty 404 from the
proxy.
The start-from-now helpers in the reference clients need this release.
Added /agents.md, /api.md, /llms.txt, an OpenAPI 3.1 file, a JSON Schema and labelled illustrative samples. All are checked against one fact sheet.
Corrected the error documentation: errors carry their code in the
error field, and every code is now listed
with its status and what to do. No change to the API itself.
Facts version 2026-11-10.3: the billing routes are now listed with the request, short-window and storage errors they share with the other routes; error lists are described as shared by a route family rather than by a single operation; and the three provider-webhook-only codes are named with their status. No change to the API itself.
Documented that a market-filtered page can be empty while
has_more is true, that coverage reports screening status as
unknown with no backfill, and how often each plan can poll.
Anyone can sign in with Google and create an API key. Free is 100 news responses per UTC day. An optional seven-day trial and the Builder plan (USD 29 a month) allow 5,000 a day.
Published the ThroughlinePublicationV3 feed shape: cursor
reads, upserts as complete replacements and explicit withdrawals.
There is no availability, latency or coverage commitment. Nothing on this page is a promise about future changes.