PoeOS Hub APIPoeoshub.life ↗
Get per-network transaction costs, block times, finality windows, and live RPC health for Base, Arbitrum, Ethereum, and Solana via the PoeOS Hub API.
What is the PoeOS Hub API?
The PoeOS Hub API exposes one endpoint, list_network_fees, that returns up to four blockchain network rows combining published cost models with a live RPC health check per network. Each row includes average transaction cost in USD, block time, finality window, native currency, chain ID, flash-loan availability, RPC status, and latency — giving developers a single call to compare fee economics and node health across Base, Arbitrum One, Ethereum, and Solana.
curl -X GET 'https://api.parse.bot/scraper/4b0bc435-81ce-4ef9-b384-975e0060ea10/list_network_fees?network=ethereum' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace poeoshub-life-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: PoeOS Network Fees — list supported chains with live health and cost data."""
from parse_apis.poeoshub_life_api import PoeosHub, ParseError
client = PoeosHub()
# List every supported network and print its cost model + live status.
for net in client.networks.list(limit=10):
print(f"{net.name} ({net.family}): ~${net.avg_tx_cost_usd} per tx, "
f"status={net.live_status}, latency={net.live_latency_ms}ms")
# Narrow to a single chain by id and inspect its RPC health details.
try:
eth = client.networks.list(network="ethereum", limit=1).first()
except ParseError as e:
# Upstream structure changed or extraction failed
print(f"Parse error ({e.code}): {e}")
else:
if eth is not None:
print(f"\n{eth.name} detail:")
print(f" Chain ID: {eth.chain_id}")
print(f" Finality: {eth.finality}")
print(f" Flash loans: {eth.flash_loans}")
print(f" Provider: {eth.provider}")
print(f" Latest block: {eth.live_block}")
print(f" Checked at: {eth.checked_at}")
print("\nexercised: networks.list")
Returns one row per supported blockchain network combining the site's published cost model (average transaction cost in USD, block time, finality window, chain id, native currency, flash-loan availability) with a live health check made by the site at call time (RPC status, latency in ms, latest block/slot, provider, timestamps). The result is the full registry of 4 networks in a single call; the optional network filter narrows it to one row and an unknown network id yields an empty list. avg_tx_cost_usd is the site's published estimate, not a live gas-price quote; the site does not publish a historical gas series. Fields chain_id and flash_loans are null for Solana (SVM).
| Param | Type | Description |
|---|---|---|
| network | string | Network id to return only that row. Confirmed ids: base, arbitrum, ethereum, solana (case-insensitive). Omitted = all networks. |
{
"type": "object",
"fields": {
"note": "provenance note on avg_tx_cost_usd",
"count": "number of rows returned",
"networks": "array of network rows, each with id, name, family (evm|svm), chain_id (null for svm), native_currency, block_time_sec, finality (text), avg_tx_cost_usd (site cost model), flash_loans (null when not applicable), rpc_url, explorer_url, configured_status, live_status, live_latency_ms, live_block (text), provider, checked_at, last_success_at"
},
"sample": {
"data": {
"note": "avg_tx_cost_usd is the site's published per-network cost model; historical gas series is not published by the site.",
"count": 1,
"networks": [
{
"id": "ethereum",
"name": "Ethereum",
"family": "evm",
"rpc_url": "https://ethereum-rpc.publicnode.com",
"chain_id": 1,
"finality": "~13m",
"provider": "Alchemy (dedicated)",
"checked_at": "2026-09-22T04:39:51.199Z",
"live_block": "Block #26,030,703",
"flash_loans": "Aave v3 adapter",
"live_status": "operational",
"explorer_url": "https://etherscan.io",
"block_time_sec": 12,
"avg_tx_cost_usd": 3.1,
"last_success_at": "2026-09-22T04:39:51.376Z",
"live_latency_ms": 177,
"native_currency": "ETH",
"configured_status": "degraded"
}
]
},
"status": "success"
}
}About the PoeOS Hub API
What the API Returns
The list_network_fees endpoint returns an array of network rows under the networks key, alongside a count of rows and a provenance note describing how avg_tx_cost_usd is sourced. Each network row contains: id, name, family (either evm or svm), chain_id (null for Solana), native_currency, block_time_sec, finality, flash-loan availability, RPC status, and latency measured at call time.
Filtering by Network
Pass the optional network query parameter to restrict results to a single chain. Accepted values are base, arbitrum, ethereum, and solana (case-insensitive). Omitting the parameter returns all four rows. This is useful when your application only needs to compare fee costs for a specific chain without parsing the full payload.
Live Health vs. Static Cost Data
The response blends two distinct data categories. The cost model fields — avg_tx_cost_usd, block_time_sec, finality, and flash-loan availability — reflect PoeOS Hub's published figures for each network and carry a provenance note. The RPC health fields — status and latency — are measured live at the time of each API call, so repeated requests may return different latency readings as network conditions change.
The PoeOS Hub API is a managed, monitored endpoint for Poeoshub.life — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when Poeoshub.life changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official Poeoshub.life API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Display current average transaction costs across EVM and SVM chains in a cross-chain DeFi dashboard.
- Alert users when RPC latency for a specific network exceeds a threshold before they submit a transaction.
- Filter for flash-loan-capable networks to dynamically route arbitrage strategies.
- Compare block times and finality windows to select an optimal chain for a time-sensitive smart contract deployment.
- Monitor RPC status for Base, Arbitrum, Ethereum, and Solana in a unified infrastructure health dashboard.
- Surface native currency and chain ID metadata for wallet or explorer tooling that needs per-chain configuration.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does PoeOS Hub have an official developer API?+
What does the `list_network_fees` endpoint return for each network?+
id, name, family (evm or svm), chain_id (null for Solana), native_currency, block_time_sec, finality window, flash-loan availability, and live RPC status and latency captured at call time. A top-level note field describes the provenance of avg_tx_cost_usd.How current is the transaction cost data?+
avg_tx_cost_usd and related cost-model fields reflect figures published by PoeOS Hub and carry a provenance note in the response. They are not tick-by-tick gas price feeds. The RPC health fields — status and latency — are measured live on each request and will vary between calls.