Provided by TikHub
X post comments, first batch
Comments under one X post by tweet_id: data.thread holds the comments (13 came back for a post with 25 replies) and data.replies is the reply count, not a list. The response carried no cursor in testing, so further pages are unverified. 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_post_comments on Glasser.glasser run -p tikhub -e '/api/v1/twitter/web/fetch_post_comments' -i '{"tweet_id":"1835124037934367098"}' --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_post_comments","input":{"tweet_id":"1835124037934367098"},"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_post_comments 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": [
"tweet_id"
],
"properties": {
"cursor": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Cursor, default is None, used for paging, obtained from the last request"
},
"tweet_id": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Tweet ID"
}
},
"additionalProperties": false
}{
"tweet_id": "1835124037934367098"
}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 |