Provided by TikHub
WeChat wechat channels account info
Wechat channels account info 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_channel_info on Glasser.glasser run -p tikhub -e '/api/v1/wechat_channels/v2/fetch_channel_info' -i '{"username":"v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder"}' --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_channel_info","input":{"username":"v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder"},"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 assess a prospect for outreach, you might compare their profile with your criteria and note which details still need verification.
Copy this prompt into your agent to review a profile against your outreach criteria.
Use tikhub:/api/v1/wechat_channels/v2/fetch_channel_info on Glasser.
Check this profile against my outreach criteria and flag facts I still need to verify.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"username"
],
"properties": {
"raw": {
"type": "boolean",
"description": "Optional, default True. True=raw response; False=simplified parsed structure."
},
"username": {
"type": "string",
"maxLength": 2048,
"minLength": 1,
"description": "WeChat Channels finder username (`v2_…@finder` format), e.g. `v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder` (People's Daily). - How to get it: - The `username` field of each video object in `fetch_video_detail` / `fetch_user_videos` responses (most common) - `fetch_channel_id_to_username`: convert a Channel ID (`sph…` short ID, e.g. `sphi9BjV8GK0Zsl`) into a finder username"
}
},
"additionalProperties": false
}{
"username": "v2_060000231003b20faec8c6e4811dc1d4c602ee30b0771bbcf220c67926bb76ab7702ac335a53@finder"
}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 |