Forum

Governance forum posts across 59 protocols — the discussion layer behind every DAO proposal.

60,000+governance posts

59 forums behind one endpoint. The record is the post, not the thread — title and url point to the top of the thread on the protocol's Discourse (or similar), and the author is the Discourse handle.

What's in a record

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

id
hash
title
url
author
published_at
image
source

{
  "id": 411649,
  "hash": "cce0b0650f82ef70c709577a235030e257a1a686cc7f992c08e54b9298cf8cdc",
  "title": "RSR Unlocking - a brief recent history",
  "url": "https://forum.reserve.org/t/rsr-unlocking-a-brief-recent-history/1652",
  "author": "reserve_forum",
  "published_at": "2026-09-18T07:02:00Z",
  "image": null,
  "source": {
    "name": "Reserve Forum",
    "slug": "reserve_forum",
    "icon": "https://cdn.alphaday.com/media/icons/sources/Reserve_protocol_logo_mZsCDuv.png"
  }
}

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/forum/?tags=arbitrum\&limit=3

MCP tools

get_forumget_forum_detailget_trending_forum

What it's for

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

Joining a DAO proposal to its underlying discussion: ?tags=arbitrum returns 2,170 governance posts; pair with the DAO snapshot endpoint on the same slug to reconstruct the deliberation, not just the vote.
Detecting when a forum is being brigaded or quiet — the published_at per post is real and a daily count per source is a single group-by.
Researching a protocol's history of contentious proposals: every post carries its source forum's slug, so a 'what did Reserve argue about' query is a filter on one source.

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.

No sentiment, likes or bookmarks on this endpoint.

Walked one record on 18 Sep 2026: forum records carry only id, hash, title, url, author, published_at, image, source. The news endpoint's sentiment, is_bookmarked, is_liked, likes fields do not exist here — the schema is intentionally leaner. Treat a client that expects news-shaped records as broken against this endpoint.

author is the Discourse handle, not a human name.

The example record above carries author: "reserve_forum" — a bot or community handle, not a person. The endpoint does not link handle → human identity; do not build a byline view from it.

sources needs the slug.

Verified on 18 Sep 2026: ?sources=reserve returns 0, ?sources=reserve_forum returns 544. Same shape as the news endpoint — the slug from any record's source.slug is the parameter value.

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)