Provided by TikHub
X user replies, one page
One page of an X user's Posts & replies tab, newest first: about 40 items per page. It holds every reply the user wrote to others (X search returns few of them), and each page also carries the posts being replied to: keep the items whose author.screen_name is the user's. It holds only some of the user's own posts; for those use /api/v1/twitter/web/fetch_user_post_tweet. The two tabs together can still miss a few posts: for every post of an account in a period, also run /api/v1/twitter/web/fetch_search_timeline with from:handle, since: and until:, and merge the three by post id. Pass data.next_cursor back as cursor for the next page. A provider 400 saying 'Request failed. Please retry' means the handle does not exist, the account has no posts, or TikHub's X path is down: retry once before switching Endpoints. One request per call; TikHub bills the request whether or not data comes back, and an empty data envelope is reported as no result.
How to run it
Step 1Set up
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.md
Show me how to use the TikHub endpoint /api/v1/twitter/web/fetch_user_tweet_replies on Glasser.glasser run -p tikhub -e '/api/v1/twitter/web/fetch_user_tweet_replies' -i '{"screen_name":"elonmusk"}' --endpoint-version 1Uses endpoint version 1. Inspect the current price before running. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"tikhub","endpoint":"/api/v1/twitter/web/fetch_user_tweet_replies","input":{"screen_name":"elonmusk"},"endpoint_version":1}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Uses endpoint version 1; inspect the current price before running.
Step 2Try a specific example task
When you need to plan a follow-up post, you might look for recurring questions in the comments to understand what your audience still wants to know.
Copy this prompt into your agent to find audience questions for a follow-up post.
Use tikhub:/api/v1/twitter/web/fetch_user_tweet_replies on Glasser.
Find recurring questions in these comments so I can plan a follow-up post.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"screen_name"
],
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Cursor, default is None, used for paging, obtained from the last request"
},
"screen_name": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Screen Name, for example: elonmusk, can be obtained from the user's homepage link, for example: elonmusk in https://twitter.com/elonmusk"
}
},
"additionalProperties": false
}{
"screen_name": "elonmusk"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How pricing works
| Data returned or no match | The same price with or without matching data. | $0.0011 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |