Application Developers

Most developers just need an RPC endpoint. Pocket Network provides decentralized, multi-chain blockchain data access — and for most use cases, getting started takes about 60 seconds.

Quick Start: Get an RPC Endpoint

Pocket’s public portal at api.pocket.network provides free, no-API-key-required access to 60+ blockchain networks. Drop the endpoint URL into your existing code and go:

# Ethereum mainnet
curl -X POST https://eth.api.pocket.network \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

// ethers.js — just change the URL
import { JsonRpcProvider } from "ethers";
const provider = new JsonRpcProvider("https://eth.api.pocket.network");
const blockNumber = await provider.getBlockNumber();

# web3.py — same idea
from web3 import Web3
w3 = Web3(Web3.HTTPProvider("https://eth.api.pocket.network"))
print(w3.eth.block_number)

The endpoint pattern is https://{chain-slug}.api.pocket.network. For the full list of supported chains and their slugs, see Supported Chains.

Building Something Heavier?

If you need more than a consumer endpoint — your own gateway, custom routing, dedicated access, or high-volume production traffic — PATH is the SDK for Shannon.

PATH gives you out of the box: QoS-based endpoint selection, multi-chain routing, session management, proof generation, reputation scoring, and Helm-based production deployment.

See Building with PATH for the full picture, or jump to the PATH section for installation and architecture docs.

What’s in This Section

• Supported Chains — All available chains with endpoint URLs
• Application Staking — Stake POKT for dedicated, higher-throughput access
• Integration Examples — Drop-in code for ethers.js, web3.py, wagmi, viem, curl
• Building with PATH — When and how to use PATH as your SDK
• AI Agents & MCP — Pocket as an AI agent data layer
• API Reference — OpenAPI specs for poktroll and PATH