DeGov Agent API publishes machine-readable DAO governance data across proposals, votes, voters, forum topics, events, and curated signals. Public metadata and DAO discovery routes are available without a partner token; paid routes use x402 USDC on Base or a DeGov partner token. This public source profile is editorial evidence only, while current PubFi routeability comes from the live signed Registry
The page is an AI/Codex-processed public Provider Profile and does not claim PubFi integration, gateway access, x402 payment, or MCP tooling.
Key facts
Auth
None, Partner Token, X402
Pricing
Freemium
Agent actionability
Editorial only; runtime status separate
PubFi gateway
Available in the active Registry
Last verified
Provider-sourced facts
Primary coverage
DAO proposals, votes, voters, forum topics, events, and curated signalsSource
Public routes
Pricing metadata, data-status metadata, DAO listing, and DAO detail routes are public in the provider OpenAPISource
Paid access
Paid routes settle per request through x402 USDC on Base or accept a DeGov partner tokenSource
Editorial freshness
Provider-owned OpenAPI, pricing metadata, and data-status metadata were re-read on 2026-08-26Source
PubFi execution authority
Current PubFi routeability is determined only by the live signed Registry snapshot and matching runtime OpenAPISource
Best fit and tradeoffs
Best for
DAO proposal and vote analysis
Governance-agent workflows that join on-chain and forum evidence
They need a normalized API surface across DAO proposals, votes, voters, forums, events, and governance signals.
They want agent-oriented governance records without treating every community source as the same contract.
They need an explicit per-request x402 or partner-token access path for paid governance routes.
Watchouts
General market-price aggregation
Low-level blockchain RPC access
DeGov is specialized for DAO governance workflows and does not replace market-data, general RPC, or broad explorer APIs.
The provider data-status endpoint can report backfilling or partial coverage, so current upstream health and coverage must be read separately from route availability.
Paid routes require either x402 payment on Base or a DeGov partner token; public metadata routes do not prove that every route is free.
Why teams choose it
DeGov Agent API is a machine-readable DAO governance source for proposals, votes, voters, forum topics, events, and curated signals. Its provider-owned OpenAPI describes public metadata and DAO discovery routes plus paid routes that settle through x402 USDC on Base or accept a DeGov partner token.
For Discovery readers, DeGov is a governance-specific API rather than a general market-data, RPC, or chain explorer product. Public editorial evidence can describe its source shape and access model, but the active signed PubFi Registry remains the only authority for current PubFi routes, methods, billing, and readiness. Provider health is a third, independent observation from PubFi Status.
The currently installed signed Registry generation contains an executable route for this provider. The same generation drives request matching, runtime OpenAPI, and this public view.
The provider lists /v2/meta/pricing, /v2/meta/data-status, /v2/daos, and /v2/daos/:daoId as free routes.
Paid rate limit
Four public routes plus 0.005 and 0.01 USDC per-request paid tiers: Verified from the provider-owned pricing inventory; access remains provider-controlled
Data shape
Data types
Daos, Proposals, Votes, Voters, Forum Topics, Events, Signals
Inspect the selected route's provider OpenAPI security and live PubFi billing contract before choosing x402 or partner-token access.
Freshness
Medium
Read provider data-status independently from Registry readiness because upstream coverage can be degraded while PubFi still has ready route variants.
Schema
Medium
Preserve the route-specific proposal, vote, voter, forum, event, and signal response contracts instead of flattening them into one universal governance schema.
Use cases
Monitor governance proposals and voting activity
Resolve DAO, proposal, voter, forum, event, and signal records for agents
Comparison snapshot
Compare DeGov with Subscan when the workflow is governance-specific: DeGov focuses on DAO proposals, votes, voters, forums, events, and signals across supported communities, while Subscan focuses on indexed Substrate and Polkadot explorer-style account, extrinsic, staking, asset, and governance reads.
PubFi friction relief
Auth
Source friction
The provider OpenAPI distinguishes public routes from paid routes that use x402 USDC on Base or a partner token.
PubFi relief
Discovery states the provider access model while the live Registry supplies the exact PubFi route and billing contract at request time.
Other
Source friction
The provider data-status endpoint publishes a coverage state and data-as-of timestamp independently from its API schema.
PubFi relief
Discovery keeps editorial freshness, Registry availability, and provider health as separate evidence layers.
DeGov API is a source for DAO proposals, votes, voters, forum topics, events, and curated governance signals.
Does every DeGov route require a partner token?
No. Provider metadata and DAO discovery routes are public. Paid routes use x402 USDC on Base or a DeGov partner token according to the provider OpenAPI.
Is DeGov available through PubFi?
Inspect the live PubFi Registry and runtime OpenAPI. This editorial profile does not establish current execution by itself.
