DAO governance

Live and historical governance proposals across DAOs, each with the voting window attached — the one crypto event you cannot catch up on afterwards.

6,600+proposals

Every record carries starts_at and ends_at, which is what makes "can I still vote on this" answerable. Read the limits before relying on the active filter to answer it for you.

What's in a record

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

id
hash
title
url
starts_at
ends_at
image
source

{
  "id": 8443,
  "hash": "60b76edbdb9d7dda6737cc89763dcbe1740477756358c0dd025f4fd6dafe38b6",
  "title": "Rotate Sentinel Addresses on the DUNI-Owned Uniswap Earn Vaults",
  "url": "https://snapshot.org/#/uniswapgovernance.eth/proposal/0x...",
  "starts_at": "2026-09-18T20:00:00Z",
  "ends_at": "2026-09-23T20:00:00Z",
  "image": null,
  "source": {
    "name": "Uniswap",
    "slug": "uniswap_dao",
    "icon": "https://cdn.alphaday.com/media/icons/sources/uniswap.jpg"
  }
}

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/dao/?sources=arbitrum_dao

MCP tools

get_daoget_dao_detailget_trending_dao

What it's for

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

Deadline alerting, which is the whole point: a proposal closing in six hours cannot be acted on retroactively, and ends_at makes "closing soon" a computation rather than a subscription.
Scoping to one DAO: ?sources=arbitrum_dao returns that DAO's own proposals, where ?tags=arbitrum returns the wider Ethereum-ecosystem set.
Joining a vote to its discussion: the forum capability covers the same protocols, so a proposal and the debate behind it can be reconstructed from two calls on the same slug.

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=true returns nothing on the public API.

Verified 20 Sep 2026: ?active=true returns 0 while 6 of 200 sampled proposals are provably open (starts_at <= now <= ends_at). It is fixed on the dev API and verified there, but not yet live here. Until it ships, compute the window yourself from the two date fields — which is what /cookbook/dao-proposal-alerts does.

?period= does nothing here.

period filters on published_at, and proposals have no such field — they carry a date range instead. On the public API the parameter passes through silently and returns the whole corpus, so a "proposals this week" query built on it is quietly wrong. Window on starts_at / ends_at.

Titles are not unique.

Distinct proposals routinely share a title prefix — a DAO batching three related votes will file three near-identical titles. Identify on hash or url; use the title only to display, and do not truncate it for deduplication.

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)