Events

Conferences, meetups, hackathons and community calls with dates, locations and a type code on every record.

6,500+events

item_type classifies each one — EDU, MU (meetup), Co (conference), Hk (hackathon) and a handful more. location is populated on 96% of records.

What's in a record

Every field the corpus returns for one record. Real shape — walked corpus-wide, not sampled.

id
hash
title
item_type
starts_at
ends_at
location
is_subscribed

{
  "id": 6288,
  "hash": "a4c1e0b7f3d25a918e6b0c4d7f2a83915ec0d4b6",
  "title": "Valley of the Commons",
  "item_type": "Co",
  "starts_at": "2026-08-24T00:00:00Z",
  "ends_at": "2026-09-20T00:00:00Z",
  "location": "Zurich, Switzerland",
  "is_subscribed": false
}

Get it

A curl that runs against the live API right now, plus the MCP tool names for the same data.

curl https://api.alphaday.com/items/events/?item_type=Hk

MCP tools

get_eventsget_events_detailget_trending_eventsget_events_this_week

What it's for

Three concrete questions this capability answers that a general crypto API does not.

A filtered calendar without scraping event sites: item_type separates hackathons from conferences from meetups, so "hackathons in the next quarter" is one call plus a date comparison.
Travel and presence planning: location is a real string on 96% of records, so a city or region filter needs no geocoding step.
Multi-day handling that most calendars get wrong: starts_at and ends_at are both present, so a week-long conference renders as a span rather than a point.

Known limits

Required, not optional. Coverage gaps, staleness and parameter traps that were observed by running the curl above against the live server on 2026-09-18.

?active= does not partition on the public API.

Verified 20 Sep 2026: ?active=true returns 864 and ?active=false returns 6,568 — the entire corpus — against a total of 6,568. The two sets overlap, so paginating "inactive" events returns active ones mixed in. Fixed on the dev API and verified there; not yet live here.

?period= is silently ignored.

Same cause as on governance: period filters on published_at, and events carry a date range instead. The parameter neither narrows nor errors on the public API. Window on starts_at / ends_at.

item_type includes an undocumented placeholder.

Over 600 rows the values are EDU (259), MU (161), Co (118), Hk (26), CC (11), *** (11), WK (9), PY (3) and PR (2). The *** entries are a placeholder rather than a category — filter them out of anything user-facing, and treat the enum as open rather than fixed.

Figures and payloads verified against the live API on 2026-09-18. The API needs no key and no signup — see the full endpoint reference and the MCP server.

All 22 capabilities Cookbook: worked use cases

The crypto data layer for humans, apps, and AI agents.

Product

Launch app Dashboards API & MCP Docs Pulse Recipes

Company

Blog Contact Give Feedback Terms of Use Privacy Policy

Crypto 101

What is Bitcoin?What Is Ethereum?What is Wrapped Crypto?What is Arbitrum?What is zkSync?

Learn

Making Money with Cryptocurrency How to Build a Cryptocurrency Dashboard What Is Crypto Halving: A Bitcoin Story How To Set Up Ethereum Wallet How to Read Crypto Charts Crypto Asset Management Guide Staking vs. Liquidity Mining (Yield Farming)