> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Are Threads user replies post comments, and why does end_cursor not paginate?

> Threads fetch_user_replies returns replies authored by an account rather than comments on a post, and Threads user-list and search actions return a single unpaginated batch that ignores end_cursor.

No. `fetch_user_replies` returns the replies one account wrote, not the comments other people left under a post. To read comments under a specific post, open the post's detail and review the replies returned with the post. `end_cursor` does not paginate because `fetch_user_posts`, `fetch_user_reposts`, `fetch_user_replies`, `search_recent` and `search_top` declare no pagination: each call returns one batch, and passing `end_cursor` has no effect.

## How do posts, reposts and replies differ?

| Action               | Returns                   | Input     |
| -------------------- | ------------------------- | --------- |
| `fetch_user_posts`   | The account's own posts   | `user_id` |
| `fetch_user_reposts` | The account's reposts     | `user_id` |
| `fetch_user_replies` | Replies the account wrote | `user_id` |

The `fetch_user_replies` list is not the full set of comments others left on a particular post. If you only have a username, query `fetch_user_info` with `username` to get the account. If you already know the numeric author ID, pass the numeric author ID as `user_id` without another profile query.

## Can I keep passing end_cursor?

No. `fetch_user_posts`, `fetch_user_reposts` and `fetch_user_replies` explicitly declare no pagination, so `end_cursor` has no effect. Do not loop on a cursor or increment a cursor, and do not count repeated responses as new pages.

1. Save the returned batch.
2. Deduplicate by the actual record IDs.
3. Treat the batch as one snapshot, not an entire historical export. A later query produces a new snapshot, not a continuation page.

## Is recent versus top search a sort option?

No. `search_recent` and `search_top` are separate actions, and each requires `query`. Both declare no pagination and ignore `end_cursor`. To compare recent and top results, make one call to each action and record which search returned each row. Do not invent a `sort` parameter, and do not read either result as an exhaustive ranking.

## How should I prevent repeated spending?

1. Start with one target account and one list query.
2. Save `request_id`, collection time, input and raw `data`.
3. Organize and deduplicate locally; local work needs no further query.
4. Budget another list action or another search action as a separate call. A short result does not mean another page is available to buy.

For example, to see what a brand said this week, read the brand account's `fetch_user_posts` batch and use the original author to tell the brand's own posts from reposts. To see how the brand responds to customers, read the brand account's `fetch_user_replies` batch. For discussion under a specific announcement, open the announcement post's detail and review the replies returned with the post.

[Links and IDs](/faq/threads-link-or-id)