/v1/call/zhihu.followersZhihu user followers API
Only on Zhihu.
The Zhihu user followers API returns a page of the accounts following a Zhihu user, 20 a page: name, headline, avatar, follower count, answer and article counts. One call costs 2 credits ($0.004 to $0.0067 depending on the pack); failed calls are free. Call it over HTTP or from your AI client over MCP. Last tested 2026-10-17.
Last updated:
Request and response
curl https://api.socialtoai.com/v1/call/zhihu.followers \ -H "Authorization: Bearer $SOCIALTOAI_KEY" \ -H "Content-Type: application/json" \ -d '{ "username": "zhihuadmin" }'import osimport requestsresponse = requests.post( "https://api.socialtoai.com/v1/call/zhihu.followers", headers={"Authorization": f"Bearer {os.environ['SOCIALTOAI_KEY']}"}, json={ "username": "zhihuadmin", },)print(response.json())# Connected over MCP? Ask in plain words.Use the Zhihu user followers interface (zhihu.followers) with username: zhihuadmin.# Your AI calls the call tool with:{ "username": "zhihuadmin"}{ "op": "zhihu.followers", "platform": "zhihu", "status": "ok", "items": [ { "platform": "zhihu", "id": "…", "ref": "…", "approx": [], "type": "account", "username": "…", "name": "…", "url": "https://example.com/…", "bio": "…", "verified": null, "followers": 235, "following": null, "posts_count": null } ], "unavailable": ["verified", "following", "posts_count"], "page": { "has_more": true, "cursor": "cur_…", "cursor_expires_at": "2026-10-12T22:23:56.000Z" }, "cost_credits": 2}null followingnull postsNames and text were removed from the sample; the numbers are as recorded.
2 parameters.
1 required.
Send them as a JSON body with POST. Your key goes in the Authorization header, never in the URL.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| username | string | Required | — | The handle in the profile's address (url_token) |
| cursor | string | Optional | — | Pass page.cursor from the last response to get the next page. |
Where to get what you send.
usernameThe handle in the profile's address (url_token) (e.g. zhihuadmin)
Every item these return carries its username; send it as it is:
search · type=userSearch
The fields of each item.
What Zhihu cannot give is marked.
| Field | Type | Meaning |
|---|---|---|
| items[].username | string | The handle. |
| items[].name | string | The display name. |
| items[].url | string | A link to the profile. |
| items[].bio | string | The bio. |
| items[].verified | booleanalways null | Whether the account is verified. |
| items[].followers | integer | Follower count. |
| items[].following | integeralways null | How many accounts it follows. |
| items[].posts_count | integeralways null | How many posts it has published. |
nullFields Zhihu cannot giveRead null as “Zhihu did not give this”, not as zero. These are always null on this call:
verifiedWhether the account is verified.followingHow many accounts it follows.posts_countHow many posts it has published.
Every item also has platform, id, ref, approx and type; the response around the items is the same on every call. Response format
What to expect.
1 call per second per key, 5 after a purchase; going over is not charged. Rate limits
A failed call costs 0 credits and is never retried on its own. Error codes
Once connected over MCP, these questions use it.
Get a page of the accounts following a Zhihu user, 20 a page: zhihuadmin.
2 creditscall {"op":"zhihu.followers","username":"zhihuadmin"}Find Zhihu accounts about "人民日报", then for the first 3: get a page of the accounts following a Zhihu user, 20 a page.
8 creditssearch {"platform":"zhihu","query":"人民日报","type":"user"}call {"op":"zhihu.followers","username":"<username>"} × 3
The interface of the same name on other platforms.
All platforms and prices/v1/call/zhihu.followers{ "username": "zhihuadmin" }2 creditsper call