Gas Price Oracle

blockchain

Serving

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.

Endpoint: POST https://agent.pocket.network/v1/gas-price-oracle/v1/gas
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453), Tempo (eip155:4217)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/gas-price-oracle/v1/gas \
  -H 'content-type: application/json' \
  -d '{"chain_id":1}'

Example response

The response this call returned, captured 2026-09-21 23:47:37 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "gas-price-oracle",
    "schemaCheck": "unchecked"
  },
  "data": {
    "chain_id": 1,
    "base_fee_wei": 81710014,
    "tiers": {
      "slow_wei": 69453511,
      "standard_wei": 81710014,
      "fast_wei": 102137517
    },
    "gwei": 0.0817,
    "as_of": "2026-09-21T23:47:36Z",
    "source": "publicnode RPC (live read)",
    "deterministic_note": "live chain read; same block => same value"
  }
}

Try it

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.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

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.

Methods Gas Price Oracle accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/gas`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "The chain to price.",
  "properties": {
    "chain_id": {
      "type": "integer",
      "description": "EVM chain id (default 1)."
    }
  },
  "required": [
    "chain_id"
  ]
}

Response schema

{
  "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."
}