apify_weibo_user_profile $0.00625 per call
Get a Weibo user's public profile. A Weibo user's public profile with no login — screen name, description, followers/following/post counts, verification type and reason, member rank, location, company, labels and account creation date (Apify · Weibo)
For AI agents: call apify_weibo_user_profile
POST https://toll402.dev/v1/p/apify.weibo.user.profile
{
"mode": "profile",
"users": [
"2803301701"
]
}Answers 402 with x402 payment requirements; pay with any x402 client (@x402/fetch, x402 for Python, toll402-client, toll402-mcp) or send a prepaid-credits key as x-toll402-key (https://toll402.dev/credits). Paid per call via x402 (USDC on Base) or with a prepaid-credits key (x-toll402-key, card at /credits); charged only on success. Start at /llms.txt or connect the MCP server:
npx -y toll402-mcp · remote https://toll402.dev/mcp.Input schema
{
"type": "object",
"properties": {
"mode": {
"type": "string",
"description": "must be `profile` for this entry — it selects the mode",
"examples": [
"profile"
]
},
"users": {
"type": "string",
"description": "one per entry: numeric uid, screen name, custom domain or profile URL — one profile row each",
"examples": [
[
"2803301701"
]
]
},
"proxyUrls": {
"type": "string",
"description": "leave empty to use the residential proxy included in the run price; or pass your own gateway URLs (http://user:pass@host:port)"
}
},
"additionalProperties": true,
"required": [
"mode",
"users"
],
"description": "the response is the dataset items array directly — no run envelope, no polling. No login and no cookies needed from the caller. The same actor serves apify.weibo.search.posts, .trending.hot_search, .user.posts, .user.profile, .post.detail and .post.comments; `mode` selects which, and a field that belongs to another mode is rejected rather than ignored. Each row carries uid, screen_name, url, descr"
}
MCP
{"mcpServers":{"toll402":{"command":"npx","args":["-y","toll402-mcp"],"env":{"TOLL402_WALLET_KEY":"0x..."}}}}