
# Changelog

What changed in the API, the MCP server and these docs, newest first. Dates are UTC.

A fix that answers a support request is also confirmed by email, in the thread of that request.

## 17 November 2026

**A suspended account says it is suspended.** X answers a suspended account differently from one
that never existed, and Weir now passes that on: `getXUser` and every account endpoint
(`getXUserPosts`, followers, following and the rest) answer `404` with `details.reason`
`suspended` and the message "This X account is suspended." A missing or deactivated account is
still a plain `404`. Neither is charged. A monitor that watches a suspended account names the
reason in its failed run.

**Read an Article from its own link.** `GET /v1/x/articles/{id}` (MCP `get_x_article_by_id`)
takes the number in an `x.com/i/article/` link, finds the post that shares the Article, and
returns the same as `getXArticle`: the full body as text, Markdown and X's blocks, with the post
and author. It is billed as one post; the search that finds the post is not charged. The MCP tool
also takes the pasted link itself. Before, an Article link answered `400`, because its number is
not a post id.

**Search pages on where X stops early.** X's latest search can end, with an empty page or no
cursor, while older posts still match. `searchX` (sort `latest`) now keeps the oldest post id it
has returned in `meta.nextCursor`, and where X's own pages run out, the next page searches again
below that post with every filter kept. The last page can come back empty; that call costs 1
credit. Cursors issued before today keep working.

**`since:` and `until:` in a query count whole UTC days.** X counted those day operators in the
time zone of the account that searched, which for Weir was Japan time. Weir now turns them into
exact bounds itself: `since:2026-11-01` starts at 00:00 UTC on that day, and `until:2026-11-02`
runs to the end of 2 November UTC, as before including its own day. That matches the `since` and
`until` fields and the search builder. Operators inside quotes or brackets, after a minus, with a
time, or dated before November 2010 still reach X as typed.

**A full-width minus excludes a word.** `猫 －犬` now searches for 猫 without 犬, the same as `-犬`.
It used to reach X as a word to find. A minus inside a word, such as `JAXA－H3`, is left alone.

**Media: only posts with a file, a `type` filter, and full-size photos.** `getXUserMedia` (MCP
`get_x_user_media`) no longer returns posts whose only media is a link preview, such as a YouTube
link, which X lists on its Media tab: on one account they were three of the first five. A new
`type` parameter (`photo`, `video` or `animated_gif`) keeps one kind, like the Photos and Videos
tabs in X's apps. A page can hold fewer posts than `limit`, and `meta.nextCursor` still leads on.
You are billed only for posts returned. Every photo `url` now carries `name=orig`, the file as
uploaded: one test photo was 2,731 × 4,096 pixels this way, against 800 × 1,200 before.

**`onlyText` leaves out what X lets through.** X applies `-filter:links` loosely: a search with
it returned posts with links, photos and quotes. `searchX` with `onlyText` now drops those from
the page, so a page can hold fewer posts than `limit` while `meta.nextCursor` still leads on.

**Replies: what X returns, said plainly.** `getXReplies` returns the direct replies to a post and
any replies to them that X shows inline, not every reply at every depth. Call it on a reply's id
for that reply's own replies, or search `conversation_id:<id>` with `searchX` for all depths.

## 16 November 2026

**Reddit says when it is refusing us.** Reddit has refused requests from Weir's servers since
3 November. While the last three hours show that, a failed Reddit call answers `503` with
`details.reason` `reddit_refusing`, a `Retry-After` of 30 minutes, and a message that says why and
that the call was not charged. The MCP server's Reddit tools say so at the start of their
descriptions, and the status page shows Reddit's outage over three hours when fifteen minutes hold
too few calls to judge. It all clears on its own once Reddit answers again. X is not affected.

**The buy page shows prices before sign-in.** https://weirapp.io/buy lists the packs to anyone, and
asks to sign in only to pay. The button in a low-balance or out-of-credits email now pays for that
account without signing in.

## 12 November 2026

**The out-of-credits error says what to do.** A `402` for an empty balance now names the day the
month's free credits return and the price of the smallest pack, and links to a page that only sells
packs, https://weirapp.io/buy (from $5). `details` carries the same as fields: `buyUrl`, `smallestPack` and
`freeCreditsRenewAt`. MCP tools hand that sentence to the model, where they used to say a fixed
"out of credits" for every `402`, including an account on hold. See
[`402` and `429` are opposites](/errors#402-and-429-are-opposites).

**Low-balance emails for accounts that have bought credits.** You get one email when less than a
fifth of your last pack is left, and one when the balance reaches zero. Free accounts keep their
two emails, at 80% used and at used up, and both now open the payment page directly. From December
a free account whose calls are still being refused two days after the used-up email gets one
reminder. See [running out](/billing#running-out).

**Which email sign-ups start with 1,000 free credits.** It is now another recent account on the
same private email domain, one mailbox written in different ways, an address at a throwaway email
service, or a newly registered domain that runs its own mail server. Addresses at the usual mailbox
providers and at universities are never limited this way, and Google and GitHub sign-ups never
are. Linking Google or GitHub under Billing, or any purchase, still unlocks the full 5,000. The
check looks up the domain of the address, which takes a few seconds: a new workspace on its own
domain can show 1,000 credits at first and 5,000 a moment later. See
[free accounts and shared capacity](/billing#free-accounts-and-shared-capacity).

## 11 November 2026

**User timelines end cleanly.** X keeps the newest 800 posts on an account's Posts tab and the
newest 3,200 on Posts & replies. Where a tab ends, `GET /v1/x/users/{user}/posts` and
`GET /v1/x/users/{user}/replies` (`get_x_user_posts`, `get_x_user_replies`) now return
`nextCursor: null`. Before, X's pinned post came back again and again as a page of its own, and
paging ended in an error. The pinned post is on the first page only. See
[how far back an X account goes](/pagination#how-far-back-an-x-account-goes).

**Full pages while paging a timeline.** X bundles a thread into one entry, so a page of 20 often
held 21 to 28 posts, and the few left over came back as a page of their own: every other call
returned 1 to 8 posts. A page is now filled up to `limit` from the next one. The same posts take
about half the calls.

**Monitors ask X twice.** X's search sometimes answers "nothing" for a search that has results. A
monitor run now asks a second time when the first answer is short of a full page, and merges the
two, so a post is not left for the next run. Nothing to change in your [monitors](/monitors).

**Free accounts wait less.** Part of X's capacity is kept for workspaces that have bought credits.
That part now shrinks as each fifteen-minute window runs out when paying customers are not using
it, and an account making its first few calls is served before heavier use. The `Retry-After` on a
`free_capacity` refusal is the moment capacity returns, not the end of the window. See
[free accounts and shared capacity](/billing#free-accounts-and-shared-capacity).

## 9 November 2026

**Paying customers are served first when X is busy.** X limits how many requests each of our
connections may make in fifteen minutes. A free call beyond the free share of that now gets `429`
with `details.reason` of `free_capacity` or `free_account_share` and a `Retry-After`, and is never
charged. Two more reasons can reach any account: `heavy_account` and `source_capacity`. All four
are in [Billing](/billing#free-accounts-and-shared-capacity).

**One free allowance per person.** Free accounts that look like several accounts run by one
person get `402` with `details.reason: "free_credit_hold"`. Buying any credit pack lifts it at
once, and an email to support lifts one made in error. Some new email sign-ups start with 1,000
free credits a month and get the full 5,000 by linking Google or GitHub under Billing in the
dashboard.

**Twice the X capacity.** We doubled the number of X connections the API reads through.

## 8 November 2026

**Search reads `OR` the way you wrote it.** X applies `AND` before `OR`, so a query such as
`cats OR dogs` combined with another filter (`fromUsers`, `minLikes`, a date) used to apply that
filter to `dogs` only. The query is now grouped first, and the filter applies to both.

**Clearer "not found" for posts through MCP.** The message now says what it can mean: the post was
deleted, the account is suspended or protected, the post is withheld in some countries, or the id
is wrong.

## 4 November 2026

**Fewer "source busy" errors.** When every X connection is resting, a request now waits a few
seconds for the first one back instead of failing at once. Errors that are worth retrying carry
`Retry-After`, in seconds. See [Errors](/errors).
