Provided by TikHub
WeChat wechat channels live detail
Wechat channels live detail from WeChat via TikHub. 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/wechat_channels/v2/fetch_live_detail on Glasser.glasser run -p tikhub -e '/api/v1/wechat_channels/v2/fetch_live_detail' -i '{"live_id":"2078950291205875194"}' --endpoint-version 2Uses endpoint version 2. 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/wechat_channels/v2/fetch_live_detail","input":{"live_id":"2078950291205875194"},"endpoint_version":2}'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 2; inspect the current price before running.
Step 2Try a specific example task
When you need to prepare a livestream monitoring dashboard, you might collect a room’s available details as a reference for your team.
Copy this prompt into your agent to prepare a live-room reference for your dashboard.
Use tikhub:/api/v1/wechat_channels/v2/fetch_live_detail on Glasser.
Pull the returned details for my live room into a reference for our monitoring dashboard.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"live_id"
],
"properties": {
"raw": {
"type": "boolean",
"description": "Optional, default True. True=raw response; False=simplified parsed structure."
},
"scene": {
"type": "integer",
"description": "Optional, entry scene, default 5."
},
"live_id": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Live ID (numeric). Source: replay items of `fetch_live_history`, live entry, or live share. E.g. `2078950291205875194`."
},
"finder_username": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "Optional, anchor finder username (`v2_…@finder` format), improves hit rate. E.g. `v2_060000231003b20faec8cae1811ac4d5c702ea32b0771737aa785454f7f8177114cc4d248d66@finder` (Huxiu)."
}
},
"additionalProperties": false
}{
"live_id": "2078950291205875194"
}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.01 |
|---|---|---|
| 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 |