Grants Gateway API primary sources
Reviewed: 2026-05-10 UTC
Core project framing
- https://grants.daostar.org/
- Live DAOstar-hosted site shell for the OpenGrants / Grants Gateway analytics surface.
- https://github.com/metagov/Grants-Gateway-API
- Official repository for the dashboard / API implementation.
- https://raw.githubusercontent.com/metagov/Grants-Gateway-API/main/README.md
- Main source for architecture claims in this pass: aggregation scope, analytics endpoints, systems configuration, proxy endpoints, and security posture.
What the primary materials say
- The repository README describes the project as a comprehensive grant analysis dashboard that aggregates data from multiple grant systems across the Ethereum ecosystem using the DAOIP-5 metadata standard.
- The clearest implementation detail worth retaining is the centralized
server/config/systemsConfig.tsfile. The docs say active-system status is managed there, public APIs expose only enabled systems, and no system-modification API exists. This means the practical ecosystem view is curated by maintainers. - The README repeatedly emphasizes proxy endpoints for upstream OpenGrants and DAOIP-5 resources. That shows the gateway is not just a visualization layer; it is also a compatibility and normalization layer.
- The
sourcetaxonomy (opengrants,daoip5,custom) is analytically important because it reveals the system as an adapter framework for heterogeneous grants-data publication methods. - The dashboard claims to compare funding totals, application counts, approval rates, and historical trends across systems. That makes the project a metric-and-narrative layer above metadata publication.
- Supported / activatable systems listed in the README matter less as stable facts than as evidence that the gateway is designed around maintainable inclusion and exclusion decisions rather than total automatic discovery.
Why it matters for the corpus
- Grants Gateway API is a useful downstream comparison point for DAOIP-5 because it shows where shared metadata standards turn into maintained registries, translation code, and ecosystem dashboards.
- It helps separate at least three layers that are often blurred together in grants infrastructure: metadata publication, registry/indexer policy, and analytics / narrative production.
- The reusable insight is that even when grant data is standardized, practical legibility still centralizes around whoever curates system lists, maintains field mappings, proxies upstream data, and chooses headline metrics.