# Events data API for AI agents: from $0.001 per call ($1 per 1,000), no subscription

> Whizbrew's Events 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 Events data: 7 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](https://whizbrew.com/api), [all tools](https://whizbrew.com/tools?a=588ce491e7fd), [pricing](https://whizbrew.com/pricing?a=588ce491e7fd)).

## Pricing

| Tool | What it returns | Per call that returns data | Per 1,000 calls |
|---|---|---|---|
| `events.luma` | Public Luma events near a place or matching search words, with date, venue, hosts, guest count and ticket price. Pass next_cursor as cursor to read on. | $0.001 | $1 |
| `events.luma_event` | One Luma event by its link: description, date, venue, hosts with their social handles, guest count and ticket types. | $0.001 | $1 |
| `events.meetup` | Upcoming Meetup events matching search words around a city, with date, group, venue and how many are going. First results only. | $0.002 | $2 |
| `events.conferences` | Technology conferences by topic, from the open community lists of confs.tech: name, website, dates, city and country or online, the call for papers (link, deadline, still open or not) and the conference's social accounts. Topics include general, product, ux, data, devops, security, leadership, javascript, python and 23 more. By default the upcoming ones of this and next year, soonest first; filter by country, by words in the name or city, or to the ones whose call for papers is open (where to speak or sponsor next). | $0.001 | $1 |
| `events.hackathons` | Open and upcoming hackathons listed on Devpost: title, link, submission dates, time left, place or online, prize amount, number of cash prizes, registrations, themes and the organiser. One read of devpost.com's public hackathon list (9 a page, in the site's order); no login. Useful to find where developers of a topic gather or where to sponsor. Nothing found is an empty list. | $0.001 | $1 |
| `events.dev_events` | Upcoming developer conferences and masterclasses worldwide from the dev.events feed: name, link, date, city, country and continent or online, and topics, soonest first. One read of the site's public RSS feed, which holds about 100 upcoming events (not every event of the site); the words and the location filter look at these only. No login. Nothing matching is an empty list. | $0.001 | $1 |
| `events.tech_events` | Upcoming tech industry events as Techmeme lists them (conferences, summits, product events and the earnings dates of large tech companies): dates as the page writes them (no year), name, city and Techmeme's link to the event's site, soonest first. One read of the public page techmeme.com/events; no login. Filter by words in the name or city. Nothing matching is an empty list. | $0.001 | $1 |

## Example calls

`events.luma` ($0.001 per call): Public Luma events near a place or matching search words, with date, venue, hosts, guest count and ticket pric

```
curl -s -X POST https://whizbrew.com/v1/call/events.luma \
  -H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
  -d '{"latitude":51.5,"limit":3,"longitude":-0.12,"query":"ai"}'
```

`events.luma_event` ($0.001 per call): One Luma event by its link: description, date, venue, hosts with their social handles, guest count and ticket 

```
curl -s -X POST https://whizbrew.com/v1/call/events.luma_event \
  -H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
  -d '{"url":"https://lu.ma/p0eh6pj4"}'
```

`events.meetup` ($0.002 per call): Upcoming Meetup events matching search words around a city, with date, group, venue and how many are going

```
curl -s -X POST https://whizbrew.com/v1/call/events.meetup \
  -H "Authorization: Bearer $WHIZBREW_KEY" -H "content-type: application/json" \
  -d '{"city":"Berlin","country":"de","limit":3,"query":"rust"}'
```

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](https://whizbrew.com/status).

## Start

- **An agent on its own**: read [https://whizbrew.com/agents.md?a=588ce491e7fd](https://whizbrew.com/agents.md?src=body-text&a=588ce491e7fd). 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?a=588ce491e7fd`) 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/mcp` as 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?a=588ce491e7fd](https://whizbrew.com/llms.txt?src=body-text&a=588ce491e7fd). 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](https://whizbrew.com/app#signup), make a key, then `POST https://whizbrew.com/v1/call/<tool>` with `Authorization: Bearer <key>`.
