Weibo data API for AI agents: from $0.002 per call ($2 per 1,000), no subscription
Whizbrew's Weibo data API costs from $0.002 per call ($2 per 1,000 calls); a typical call is $0.003 ($3 per 1,000). Only a call that returns data is charged: an empty or failed call is free. There is no subscription and no monthly fee. A new account starts with $2 of free credit, with no card.
It reads public Weibo data: 10 tools, live at the moment of the call, over one API key or one MCP server (https://whizbrew.com/mcp). It is an API, not a scraper you run: no proxies, no browser and no scraping code on your side. The same key reaches 893 tools for other platforms (all APIs, all tools, pricing).
Pricing
| Tool | What it returns | Per call that returns data | Per 1,000 calls |
|---|---|---|---|
weibo.trending | Weibo trending searches with their heat, from the main board or a topic board. | $0.002 | $2 |
weibo.profile | Public Weibo profile and its counts. | $0.002 | $2 |
weibo.post | One public Weibo post with its full text, media and counts. | $0.002 | $2 |
weibo.comments | Comments on a public Weibo post, most liked first. Set "comment_id" to read the replies to one comment (the site gives a visitor the first 100 replies). | $0.003 | $3 |
weibo.likes | Accounts that liked a public Weibo post, newest first. The site shows the newest 200 only. | $0.003 | $3 |
weibo.video | One Weibo video: title, counts, length and file links. View counts are rounded by the site. | $0.002 | $2 |
weibo.user_videos | Video posts of a Weibo account, newest first. | $0.003 | $3 |
weibo.search_users | Search Weibo accounts by name. Follower counts are rounded by the site. | $0.003 | $3 |
weibo.feed | Posts on Weibo's public hot feed right now, from the main feed or one of its channels. | $0.003 | $3 |
weibo.suggest | What people search for on Weibo around some words: the search box's own suggestions. | $0.003 | $3 |
Example calls
weibo.trending ($0.002 per call): Weibo trending searches with their heat, from the main board or a topic board
curl -s -X POST https://whizbrew.com/v1/call/weibo.trending \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"board":"hot","limit":3}'
weibo.profile ($0.002 per call): Public Weibo profile and its counts
curl -s -X POST https://whizbrew.com/v1/call/weibo.profile \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"user":"1195230310"}'
weibo.post ($0.002 per call): One public Weibo post with its full text, media and counts
curl -s -X POST https://whizbrew.com/v1/call/weibo.post \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"id":"Rrxbk2ASJ"}'
Over MCP the same call is call_tool with {"tool": "<name>", "arguments": {…}}. How often each tool works, measured from real calls: https://whizbrew.com/status.
Start
- An agent on its own: read https://whizbrew.com/agents.md. It asks for a free quote (
GET https://whizbrew.com/v1/agent/guide?goal=<the task in plain words>), then one request (POST https://whizbrew.com/v1/agent/start) gives it a key that works at once with the free credit, with no email and no sign-up form. Its human claims the account later. - A chat app (ChatGPT, Claude, Gemini): add the MCP server
https://whizbrew.com/mcpas a custom connector and sign in. No key to copy. - An agent with a shell (Claude Code, Codex, Cursor): read https://whizbrew.com/llms.txt. The agent starts a pairing with one request, its user approves with one click, and the agent holds its own key.
- Plain HTTP: create an account at https://whizbrew.com/app#signup, make a key, then
POST https://whizbrew.com/v1/call/<tool>withAuthorization: Bearer <key>.