Threads data API for AI agents: from $0.003 per call ($3 per 1,000), no subscription
Whizbrew's Threads data API costs from $0.003 per call ($3 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 Threads data: 6 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 |
|---|---|---|---|
threads.profile | Public Threads profile: name, bio, follower count, verified flag. By handle or by numeric user id (id gives the username too); give one of the two. | $0.003 | $3 |
threads.posts | Recent Threads posts of an account, newest first, up to 100: its own posts, its replies or its reposts. No view counts. | $0.003 | $3 |
threads.post | One Threads post by URL or numeric post id with its counts and the replies under it. Pass next_cursor as cursor to read more replies. | $0.003 | $3 |
threads.search | Search public Threads posts by keyword, top or most recent. One page of results, no view counts. | $0.003 | $3 |
threads.search_users | Threads accounts matching a name or keyword: username, name, bio and verified flag. A Threads username is also the account's Instagram username. | $0.003 | $3 |
threads.search_tags | Threads tags (topics) matching a keyword: name, id and the link to the tag's posts. Read the posts with threads.search and in=tags. | $0.003 | $3 |
Example calls
threads.profile ($0.003 per call): Public Threads profile: name, bio, follower count, verified flag
curl -s -X POST https://whizbrew.com/v1/call/threads.profile \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"handle":"zuck"}'
threads.posts ($0.003 per call): Recent Threads posts of an account, newest first, up to 100: its own posts, its replies or its reposts
curl -s -X POST https://whizbrew.com/v1/call/threads.posts \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"handle":"zuck","limit":3}'
threads.post ($0.003 per call): One Threads post by URL or numeric post id with its counts and the replies under it
curl -s -X POST https://whizbrew.com/v1/call/threads.post \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"limit":3,"url":"https://www.threads.com/@zuck/post/DfihFPxkaZ1"}'
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>.