At a glance
Decision summary
- Best for
- Decentralized RPC routing
- Watch out for
- Exchange market data feeds
- Auth
- API key
- Pricing
- Marketplace pricing
- Agent actionability
- Not actionable
- PubFi gateway
- PubFi gateway not routeable yet
- Last verified
Pokt Network
Pokt Network is tracked as an RPC infrastructure source for Ethereum coverage. Decentralized RPC infrastructure network that routes application requests across independent node operators
Indexed onlyPublic source profile
Best fit and tradeoffs
Best for
- Decentralized RPC routing
- Infrastructure redundancy comparisons
- They want decentralized RPC infrastructure in the shortlist rather than only centralized providers.
- They need to evaluate gateway and node-operator routing models.
- They are comparing infrastructure resilience or decentralization posture alongside endpoint access.
Watchouts
- Exchange market data feeds
- Wallet portfolio normalization
- The fixture marks commercial facts as product-scope dependent, so no single provider-wide price or quota should be published.
- Pokt requires more understanding of routing and gateway model than a conventional managed RPC account.
- Teams seeking simple first-party managed support may prefer Chainstack, Infura, or QuickNode.
Why teams choose it
Pokt Network is decentralized RPC infrastructure that routes application requests across independent node operators. Discovery tracks it as Ethereum RPC infrastructure, but its network model differs from centralized managed endpoint providers.
Pokt is worth evaluating when decentralization, gateway selection, and provider-network economics matter to the application. It is less straightforward than buying a standard RPC plan from a single managed provider, so implementation planning should account for product scope and routing model.
Capability summaries
Pokt Network RPC infrastructure coverage
- Category
- RPC infrastructure
- Public status
- Requested
- Auth requirement
- API key
- Procurement state
- Free Requires Auth
- Coverage
- Ethereum
- Output contracts
- Rpc Endpoint Status
Quick-start entry
POST
Endpoint path not listed- Style
- curl
- Language
- curl
- Method
- POST
- Path
- Not listed
- Requires auth
- Yes
- Provider docs
- Documentation
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
- API key
- Pricing model
- Marketplace pricing
- Free tier
- The public API portal is open access; higher-throughput commercial terms are staking or gateway-operator scoped.
- Starting price
- Marketplace pricing
- Free rate limit
- Marketplace pricing
- Paid rate limit
- Marketplace pricing
Protocols and outputs
- Data types
- Rpc Endpoints, Decentralized Node Routing
- 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
- Provider docs
- Doc quality score
- Not listed
- Status page
- Not listed
- Public fixture status
- Current
- Raw claim-safe status
- Public source profile
- Page tier
- Tier 2
Implementation notes
Coverage
Confirm which Pokt access path and target network the workload would use before comparing it with centralized RPC providers.
Pricing
Keep commercial copy product-scope aware because the fixture does not support one flat public plan projection.
Gotcha
Document the decentralized routing model explicitly so buyers do not compare Pokt as if it were only another managed endpoint vendor.
Use case candidates
- Evaluate decentralized RPC access for application requests
- Compare infrastructure routing models before provider selection
Comparison snapshot
Pokt Network is the decentralized RPC option in the seed RPC set. It differs from Blockdaemon, Chainstack, and Ankr by network architecture rather than by a simple feature checklist.
PubFi friction reduction
Routing Model
- Source friction
- The fixture describes Pokt as decentralized RPC infrastructure across independent node operators.
- PubFi relief
- Discovery labels Pokt as a public source profile and keeps gateway/payment claims out of the page unless supported by current PubFi artifacts.
Official source links
Agent-readable resources
Alternatives and hubs
FAQ
What is Pokt Network used for?
Pokt Network is a candidate source for decentralized RPC infrastructure and node request routing.