Summary: Grants Gateway API is best understood not as another grants round product or payout mechanism, but as an aggregation and interpretation layer built on top of DAOIP-5-style funding metadata. Its primary materials describe a dashboard and API that ingest grant-system data from multiple ecosystems, normalize it into comparable system / pool / application views, proxy heterogeneous upstream sources, and expose a manually curated active-systems configuration as the practical source of truth. That makes it a useful comparison class for DAOIP-5, Open Source Observer, Questbook, and grants-program operating systems: DAOIP-5 standardizes how grants metadata can be published, while Grants Gateway shows where power reappears once someone decides which systems are live, how fields are mapped, which adapters are maintained, and which cross-system metrics become canonical.
What it does:
Aggregates grant data from multiple ecosystems and grant systems into one dashboard and API surface
Uses DAOIP-5-compatible metadata alongside OpenGrants-style upstream APIs and custom adapters
Exposes ecosystem-level analytics such as total funding, round counts, application statistics, approval rates, and cross-system comparisons
Maintains a centralized systemsConfig.ts file that determines which systems are active, their display priority, source type, and public metadata
Provides proxy endpoints for upstream APIs and static DAOIP-5 resources so downstream consumers can query one gateway instead of many inconsistent sources
Adds historical-price conversion and analytics logic so nominally separate grants systems can be compared in a shared currency and reporting frame
Key claims:
The official README frames the project as a comprehensive grant analysis dashboard that aggregates data from multiple grant systems using the DAOIP-5 metadata standard, which is the clearest reason to treat it as registry-and-comparison infrastructure rather than just an internal app.
The most important control surface is the manually edited active-systems configuration. The repo is explicit that system enable/disable operations are not exposed by API and must be changed in code, meaning the practical ontology of the ecosystem sits in a maintained allowlist rather than emerging automatically from all published DAOIP-5 data.
The presence of proxy endpoints for both OpenGrants APIs and DAOIP-5 static files is analytically useful because it shows the project is not only a dashboard. It is trying to become a compatibility layer that hides heterogeneity across funding sources and publication formats.
The README’s emphasis on field mappings, source types (opengrants / daoip5 / custom), and adapter-based ingestion shows that the real work is translation. In practice, whoever maintains those mappings decides which upstream programs are legible and comparable.
The analytics surfaces matter because once grant systems are normalized into ecosystem-wide funding totals, approval rates, and trend lines, the gateway becomes a narrative engine about which programs are active, effective, or underperforming.
This project belongs in the active corpus because it gives a concrete downstream implementation for the queue’s grants-metadata and grants-registry themes. DAOIP-5 explains how grant data can be described; Grants Gateway reveals the next layer where indexing policy, source maintenance, and metric design quietly shape what funders and researchers think the ecosystem is.
A useful caution is that the strongest surfaced materials in this pass are repository docs and a live site shell rather than a canonical spec or whitepaper. That weakens protocol-level claims but strengthens the case that this is an operational registry/indexer layer whose leverage comes from implementation choices.
Whitepaper: No canonical whitepaper surfaced in this pass. The strongest primary materials were the live DAOstar-hosted dashboard shell and the official repository README describing system configuration, proxying, analytics, and DAOIP-5 alignment; see ../whitepapers/grants-gateway-api-primary-sources-2026-05-10.md.