How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Pocket Network website screenshot

Pocket Network

Pocket Network is the decentralized RPC layer of Web3 — a permissionless, fully open data delivery protocol built on Cosmos SDK and CometBFT (the Shannon upgrade, June 2025). 5,000+ independent supplier nodes serve relays across 60-69+ blockchains, metered in compute units at $1/billion and settled on-chain in POKT under deflationary tokenomics (PIP-41, 97.5% mint ratio). Grove (grove.city) is the for-profit infrastructure company that operates the largest gateway on the network — rpc.grove.city — and maintains PATH, the open-source Go gateway any operator can run to expose Pocket Network as a single HTTP endpoint. Grove offers free no-API-key per-IP public endpoints per chain (eth.rpc.grove.city, solana.rpc.grove.city, etc.) plus paid portal applications with relay analytics and SLAs. Together they form the canonical decentralized alternative to Alchemy / Infura / QuickNode for serving JSON-RPC, REST, and WebSocket traffic to any public blockchain.

agent aware

Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.

Kin Score

API Evangelist profiles Pocket Network the way a machine reads it — 80 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Pocket Network scores 57.3/100 (strong), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Pocket Network Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Pocket Network's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/pocket-network/"
   title="Pocket Network on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/pocket-network.svg"
       alt="Pocket Network Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Pocket Network

Each block below is one kind of artifact we hold for Pocket Network. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 16

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Pocket Network Application API

Pocket application module — applications stake POKT to consume relays

Pocket Network Bank API

POKT supply, balances, and burn tracking

Pocket Network Blocks API

Block and consensus state queries

Pocket Network Consensus API

Block, header, and consensus queries

Pocket Network Gateway API

Pocket gateway module — gateways stake POKT and proxy relays for applications

Pocket Network Health API

PATH service liveness and readiness probes

Pocket Network Mempool API

Mempool inspection and broadcast

Pocket Network Proof API

Pocket proof module — claims and proofs that suppliers submit to earn POKT

Pocket Network Relays API

JSON-RPC, REST, and WebSocket relays proxied to Shannon suppliers

Pocket Network Service API

Pocket service module — services represent the data sources (EVM chains, Solana, etc.) the network serves

Pocket Network Session API

Pocket session module — sessions group applications, suppliers, and services for a given block window

Pocket Network Status API

Node status and network info

Pocket Network Supplier API

Pocket supplier module — suppliers stake POKT and serve relays via RelayMiner

Pocket Network Tokenomics API

Pocket tokenomics module — global mint, burn, and reward parameters

Pocket Network Transactions API

Transaction lookup and broadcast

Pocket Network Validators API

Staking and validator queries

Scroll within the panel for all 16 ·

Postman Collections 3

A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.

Ready-to-run Postman collections for exercising this provider's APIs.

Open Collections 20

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Scroll within the panel for all 20 ·

Arazzo Workflows 8

Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.

Multi-step API workflows described with the Arazzo specification.

Pocket Network CometBFT Node Block Inspect

Read node status for the latest height, fetch that block, then its ABCI results.

ARAZZO

Pocket Network PATH Relay Readiness

Confirm the PATH gateway is ready, then send an authenticated JSON-RPC relay through it.

ARAZZO

Pocket Network Shannon Application Balance

Look up a Shannon application, then read the on-chain balances of its address.

ARAZZO

Pocket Network Shannon Application Session

Resolve an application, confirm the target service exists, then fetch its active session.

ARAZZO

Pocket Network Shannon Block Explorer

Read the latest Shannon block height, then fetch that exact block by height.

ARAZZO

Pocket Network Shannon Service Economics

Read a service definition, the network tokenomics parameters, and total supply.

ARAZZO

Pocket Network Shannon Supplier and Gateway Survey

List suppliers, drill into the first supplier, then list gateways for network context.

ARAZZO

Pocket Network Shannon Transaction Lookup

Find the latest block, then look up a supplied transaction hash on Shannon.

ARAZZO

Scroll within the panel for all 8 ·

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.

Published pricing tiers and plan structures.

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Pocket Network Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Features 19

The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.

Notable capabilities this provider offers.

Shannon protocol — Cosmos SDK + CometBFT chain replacing Morse in June 2025
5,000+ independent nodes serving 60-69+ blockchains (EVM, Layer-2s, Cosmos, Solana)
PATH gateway (Go, MIT) — open-source single-binary gateway for any operator to run
Grove hosted endpoints — rpc.grove.city per-chain subdomains for portal and public traffic
Compute-unit metering — $1 = 1B CU, deflationary via POKT burn on every relay (PIP-41)
On-chain actors — Application, Supplier, Gateway, Validator, Source Owner
RelayMiner — supplier-side daemon proxying relays with revenue-share splits
Quality-of-Service scoring inside PATH routes around degraded suppliers automatically
Public free per-IP endpoints across every supported chain for development
99.9% uptime target on Grove public endpoints
Authenticated portal applications via opaque Application IDs in URL path
Permissionless service registration — anyone can add a new chain by staking a service
F-Chains public-data program for non-profit/public-goods consumers
$1 per billion compute units wholesale, $1 per million relays Grove pay-as-you-go (RELAY2025)
poktrolld CLI (homebrew-pocketd) for full Cosmos SDK tx/query/keys operations
Shannon SDK (Go), poktroll-clients-py (Python), shannon-tx-builder (Python)
Pocketdex (SubQuery) indexer powering Pocket Explorer
Pocket Network Foundation governance with on-chain PIP proposals
Available as decentralized RPC backend for Cosmos Keplr chain registry integrations

Scroll within the panel for all 19 ·

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Pocket Network Context

0 classes · 7 properties

JSON-LD

Spectral Rules 2

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Pocket Network API Rules

6 rules · 5 warnings

SPECTRAL

Pocket Network API Rules

8 rules · 2 errors · 5 warnings

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

Pocket Network Relay

3 properties

JSON SCHEMA

Pocket Network Shannon Actor

0 properties

JSON SCHEMA

Examples 3

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Pocket Network Authentication

apiKey · 1 scheme

SECURITY

Pocket Network Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Pocket Network Agentic Access

29 operations · 3 acting

29 operations · 3 acting

AGENTIC

Resources

Every other property we hold for Pocket Network — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 3

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 2

Authentication, authorization, and security posture

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/pocket-network · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Pocket Network, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.