x.served.fyi API

X posts and their replies. As JSON.

Posts from a list of AI researchers, labs and builders on X, each with the replies under it, collected a few times a day. Read-only, no key.

GET https://x.served.fyi/api/posts

30 requests a minute per IP · newest first · replies nested

Quick start

Ask for the latest posts. Every post comes back with its replies already attached.

curl "https://x.served.fyi/api/posts?limit=20"

# Just one account's own posts, without the replies
curl "https://x.served.fyi/api/posts?handle=simonw&kind=post&replies=0"

A post

One object per post from a followed account. Reposts and quotes point at the original.

GET /api/posts?limit=1  ·  example data
{
  "count": 1,
  "next_cursor": "MjAyNi0xMS0xMFQwOToxMjowMCswMDowMHwxOTAwMDAwMDAwMDAwMDAwMDAx",
  "posts": [{
    "id": "1900000000000000001",
    "kind": "quote",
    "handle": "ada_builds",
    "author_name": "Ada",
    "account": "ada_builds",
    "url": "https://x.com/ada_builds/status/1900000000000000001",
    "text": "Ran the new model against our eval set. 3 regressions, all in tool calls.",
    "published_at": "2026-11-10T09:12:00+00:00",
    "first_seen_at": "2026-11-10T10:40:11+00:00",
    "in_reply_to": null,
    "repost_of": null,
    "quote_of": {
      "id": "1899999999999999990", "handle": "modelco",
      "url": "https://x.com/modelco/status/1899999999999999990",
      "text": "Model Co: Our new model is out today."
    },
    "media": [{ "type": "photo", "url": "https://pbs.twimg.com/media/example.jpg" }],
    "links": ["https://example.com/evals/2026-11"],
    "reply_count": 2,
    "thread": { "fetches": 1, "last_fetched_at": "2026-11-10T11:30:02+00:00",
                "next_fetch_at": "2026-11-11T09:12:00+00:00" },
    "replies": [{
      "id": "1900000000000000007", "kind": "reply", "handle": "lin_dev",
      "text": "@ada_builds Which tool calls?",
      "in_reply_to": { "id": "1900000000000000001", "handle": "ada_builds", ... },
      "replies": [{
        "id": "1900000000000000012", "kind": "reply", "handle": "ada_builds",
        "text": "@lin_dev Mostly parallel ones. Writing it up.",
        "replies": []
      }]
    }]
  }]
}
id
The X status ID, as a string. Stable; use it to dedupe.
kind
post, quote, repost or reply. Top-level posts are never reply.
handle, author_name
Who wrote it. For a repost this is the account that reposted.
account
The followed account the post came in through. Same as handle for top-level posts.
text
Plain text of this post only. A quoted post's text is in quote_of.text, not here.
published_at, first_seen_at
When it was posted on X, and when we first stored it. ISO 8601, UTC.
in_reply_to, repost_of, quote_of
{id, handle, url} of the other post, or null. quote_of also has text.
media, links
Photos and videos as {type, url, poster}, and outside links in the text. Empty lists when there are none.
reply_count
Replies stored for this post, counting every level of the tree.
thread
When the replies were last fetched and when they will be next. null for reposts, whose replies belong to the original.
replies
The reply tree. See Replies. Left out with replies=0.
html, raw
Only with fields=full: the rendered post and the item exactly as fetched, for anything the fields above miss.

Replies

Each reply has the same fields as a post, plus its own replies, so a conversation nests as deep as it goes.

  • A reply sits under the post or reply it answers, oldest first.
  • If X didn't return the reply it answers, it sits at the top of the tree with "parent_missing": true.
  • Replies are fetched twice: when a post is about 2 hours old and again at about 24 hours. After that the tree doesn't change.
  • Each fetch gets the replies X shows first, up to about 40. Very busy posts will have more on X than here.
  • A new post has "replies": [] until its first fetch. thread.next_fetch_at says when that is.

Paging

Every response has a next_cursor. Send it back as cursor with the same filters to get the next, older page. When it is null, you have everything.

The cursor points at the last post you received, so new posts arriving while you page don't cause repeats or gaps.

import time, requests

url = "https://x.served.fyi/api/posts"
params = {"limit": 100, "since": "2026-11-01"}
posts = []

while True:
    r = requests.get(url, params=params, timeout=30)
    if r.status_code == 429:                      # over the rate limit
        time.sleep(int(r.headers["Retry-After"]))
        continue
    page = r.json()
    posts += page["posts"]
    if not page["next_cursor"]:
        break
    params["cursor"] = page["next_cursor"]

print(len(posts), "posts")

Reference

Everything is GET and returns JSON.

GET/api/posts
Posts from followed accounts, newest first, each with its reply tree.
GET/api/posts/{id}
One post with every field and its reply tree. A reply's ID works too, without a tree.
GET/api/accounts
Every followed account: posts stored, latest post, last successful fetch and any errors.
GET/api/status
Collector state: whether it is paused, the next round, requests in the last 24 hours, recent fetches.
GET/healthz
Returns {"ok": true}. Not rate limited.

Parameters for /api/posts

limit1–200
Posts per page. Default 50.
cursor
The next_cursor from the previous page.
handle
One or more followed accounts, comma-separated: handle=simonw,swyx. Not case-sensitive.
kind
post, quote or repost, comma-separated. kind=post,quote leaves out reposts.
since, until
Published at or after since and before until. A date (2026-11-10) or a date and time; UTC unless you give an offset.
q
Posts whose text contains this, ignoring case. Doesn't search replies.
replies
replies=0 leaves the reply trees out, for smaller, faster pages.
fields
fields=full adds html, raw, last_seen_at, source and conversation_id.

Errors

400
A bad parameter. The body says which: {"error": "since must be an ISO date or datetime"}.
404
No such path, or no post with that ID.
429
Over the rate limit. Wait the number of seconds in the Retry-After header, also in the body as retry_after_seconds.
503
The database is busy or not ready. Retry in a few seconds.

Limits and freshness

Rate limit
30 requests a minute per IP, with bursts of up to 20. No key and no sign-in.
New posts
Collected about every 6 hours, never between 01:00 and 08:00 IST. A post can be up to about 6 hours old before it shows up here.
Replies
Fetched at about 2 and 24 hours after a post goes up, then frozen.
Accounts
A fixed list of about 60 AI labs, researchers and builders. See the list →
Not included
Followed accounts' replies to other people's posts, likes, and anything from accounts not on the list.