Multi-chain gas price oracle: current base fee plus priority-fee tiers for EVM chains. POST /v1/gas with {chain_id} and get the base fee and slow/standard/fast tiers as one JSON object. Deterministic per read instant. Pay per request in USDC; no account, no API key.
POST https://agent.pocket.network/v1/gas-price-oracleThe first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.
Derived from the published request schema.
curl -X POST https://agent.pocket.network/v1/gas-price-oracle \
-H 'content-type: application/json' \
-d '{"chain_id":0}'This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.
{}Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.
Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.
| Method | Effect |
|---|---|
GET /v1/health | read |
GET /v1/version | read |
POST /v1/gas | read |
Published by the service itself. The example above is generated from these.
{
"type": "object",
"description": "The chain to price.",
"properties": {
"chain_id": {
"type": "integer",
"description": "EVM chain id (default 1)."
}
},
"required": [
"chain_id"
]
}{
"type": "object",
"description": "For POST /v1/gas, a JSON object with the base fee, priority-fee tiers, and the chain_id. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}Request body used in the example: {
"chain_id": 0
}