At a glance
Decision summary
- Best for
- Polkadot governance monitoring
- Watch out for
- RPC endpoint hosting
- Auth
- None
- Pricing
- No public rate card
- Agent actionability
- Not actionable
- PubFi gateway
- PubFi gateway not routeable yet
- Last verified
Polkassembly
Polkassembly is tracked as a governance source for Polkadot coverage. Governance discussion, proposal, referendum, and vote context for Polkadot and Kusama communities
AvailablePublic source profile
Best fit and tradeoffs
Best for
- Polkadot governance monitoring
- Referendum and proposal context workflows
- They need governance proposal and referendum context for Polkadot or Kusama communities.
- They want discussion and voting information alongside governance identifiers.
- They are building monitoring, research, or alerting workflows centered on governance participation.
Watchouts
- RPC endpoint hosting
- Crypto market price aggregation
- Polkassembly is specialized for governance context and should not be treated as a replacement for broad indexed chain-state APIs.
- The fixture marks public governance access, but exact high-volume terms and rate limits are not public enough to overstate.
- Teams still need to verify API shape and coverage against the specific referendum or proposal workflow they plan to support.
Why teams choose it
Polkassembly is a governance workflow source for Polkadot and Kusama community proposals, referenda, discussion, and voting context. Discovery tracks it as a governance category source rather than a generic on-chain-state API.
Its value is editorial and workflow context around governance activity. Teams evaluating Polkassembly should care less about broad chain data breadth and more about whether proposal discussion, referendum status, and vote context are the data needed for their product.
Capability summaries
Polkassembly governance coverage
- Category
- Governance
- Public status
- Available
- Auth requirement
- None
- Procurement state
- Public No Approval
- Coverage
- Polkadot
- Output contracts
- Governance Record
Quick-start entry
GET
Endpoint path not listed- Style
- REST
- Language
- HTTP
- Method
- GET
- Path
- Not listed
- Requires auth
- No
- Provider docs
- Not listed
PubFi gateway status
PubFi gateway not routeable yet
This Discovery source is available for source evaluation and comparison, but PubFi does not publish a production-callable gateway route for it yet. Use this page to compare the provider, signal demand, or start a procurement/integration review instead of attempting a PubFi gateway call.
- PubFi gateway call
- Not published for this source
- Direct gateway examples
- Not available
- Next step
- Request integration or start supplier procurement review
- Do not infer a PubFi gateway path from this Discovery page.
- Use the official provider docs for direct provider integration until a PubFi readiness entry marks this source gateway_available.
- Use the Discovery request or demand-signal CTA to register integration interest with PubFi.
- Supplier procurement, paid-plan approval, and upstream credential setup require explicit review before PubFi can route the source.
Access, pricing, and protocol metadata
Access and pricing
- Auth methods
- None
- Pricing model
- No public rate card
- Free tier
- Polkassembly documents public governance API access, while exact rate limits and high-volume terms are not publicly listed.
- Starting price
- No public rate card
- Free rate limit
- No public rate card
- Paid rate limit
- No public rate card
Protocols and outputs
- Data types
- Proposals, Referenda, Votes, Discussion Threads
- Protocols
- REST
- REST support
- Yes
- GraphQL support
- Not listed
- WebSocket support
- Not listed
- Streaming support
- Not listed
- Webhook support
- Not listed
- Feature flags
- Not listed
- SDKs
- Not listed
Provider and review status
- Documentation
- Not listed
- Doc quality score
- Not listed
- Status page
- Not listed
- Public fixture status
- Current
- Raw claim-safe status
- Public source profile
- Page tier
- Tier 3
Implementation notes
Coverage
Treat Polkassembly as governance-specific coverage; do not generalize it to balances, transactions, staking, or market data.
Docs
Review the target governance data path before implementation because proposal discussion and voting context can differ from raw chain event reads.
Rate limits
Keep throughput assumptions conservative because public high-volume API terms are not exposed in the fixture.
Use case candidates
- Track governance proposals for Polkadot ecosystem research
- Add referendum context to community or agent workflows
Comparison snapshot
Polkassembly should be compared with Subscan only for governance workflows, not for broad chain-state reads. It is the more focused governance context source, while Subscan covers broader explorer-style indexed data.
PubFi friction reduction
Scope Control
- Source friction
- The fixture maps Polkassembly to governance coverage for the Polkadot target only.
- PubFi relief
- PubFi Discovery keeps the source in the governance category and avoids turning it into a generic data API claim.
Official source links
Agent-readable resources
Alternatives and hubs
FAQ
What is Polkassembly used for?
Polkassembly is a candidate source for governance proposal, referendum, discussion, and vote context.