Hacker News data API for AI agents: from $0.001 per call ($1 per 1,000), no subscription
Whizbrew's Hacker News data API costs from $0.001 per call ($1 per 1,000 calls); a typical call is $0.001 ($1 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 Hacker News 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 |
|---|---|---|---|
hackernews.stories | Hacker News stories in rank order: the front page, or the new, best, Ask HN, Show HN or jobs list. | $0.002 | $2 |
hackernews.item | One Hacker News story, comment, job or poll by id. | $0.001 | $1 |
hackernews.user | Public Hacker News profile: karma, about text, account date and newest submission ids. | $0.001 | $1 |
hackernews.search | Search Hacker News stories or comments by words. | $0.001 | $1 |
hackernews.comments | All comments of a Hacker News story as one flat list in thread order, each with its depth and parent. | $0.002 | $2 |
hackernews.hiring | Job posts of the newest monthly Hacker News "Who is hiring?" thread, optionally only those naming a keyword. | $0.002 | $2 |
Example calls
hackernews.stories ($0.002 per call): Hacker News stories in rank order: the front page, or the new, best, Ask HN, Show HN or jobs list
curl -s -X POST https://whizbrew.com/v1/call/hackernews.stories \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"limit":3}'
hackernews.item ($0.001 per call): One Hacker News story, comment, job or poll by id
curl -s -X POST https://whizbrew.com/v1/call/hackernews.item \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"id":"8863"}'
hackernews.user ($0.001 per call): Public Hacker News profile: karma, about text, account date and newest submission ids
curl -s -X POST https://whizbrew.com/v1/call/hackernews.user \
-H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
-d '{"id":"pg"}'
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>.