13trust / 100

Data Gas Price

by pay.brianbooms.com in Onchain & crypto

x402 APIFailing, checked 2 h ago

Use when an agent needs the current gas price on an EVM chain before sending a transaction — cost estimation, fee budgeting, or deciding whether to transact now. Pass network (base, polygon, arbitrum, avalanche); returns live eth_gasPrice plus priority fee in wei and gwei from the chain's public RPC. Resale permitted: buyer may resell this data output at their own price.

GET
https://pay.brianbooms.com/api/v1/data/gas-price
Price
$0.01
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 2 h ago: Expected HTTP 402, got 400

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://pay.brianbooms.com/api/v1/data/gas-price

Each call costs $0.01 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://pay.brianbooms.com/api/v1/data/gas-price?network=EVM+chain+id.+Example%3A+base+%28default%29%2C+polygon%2C+arbitrum%2C+avalanche

Example response

The provider's example. We can't check it without paying.

{
  "data_source": "mainnet.base.org",
  "gas_price_gwei": "0.123",
  "gas_price_wei": "123456789",
  "network": "base",
  "priority_fee_gwei": "0.01",
  "product": "Gas price"
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://pay.brianbooms.com/api/v1/data/gas-price?network=EVM+chain+id.+Example%3A+base+%28default%29%2C+polygon%2C+arbitrum%2C+avalanche'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://pay.brianbooms.com/api/v1/data/gas-price?network=EVM+chain+id.+Example%3A+base+%28default%29%2C+polygon%2C+arbitrum%2C+avalanche' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fpay.brianbooms.com%2Fapi%2Fv1%2Fdata%2Fgas-price
const res = await pay("https://pay.brianbooms.com/api/v1/data/gas-price?network=EVM+chain+id.+Example%3A+base+%28default%29%2C+polygon%2C+arbitrum%2C+avalanche");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://pay.brianbooms.com/api/v1/data/gas-price?network=EVM+chain+id.+Example%3A+base+%28default%29%2C+polygon%2C+arbitrum%2C+avalanche")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoExpected HTTP 402, got 400400459 ms-
8 h agoExpected HTTP 402, got 400400347 ms-
13 h agoExpected HTTP 402, got 400400333 ms-
19 h agoExpected HTTP 402, got 400400368 ms-
25 h agoExpected HTTP 402, got 400400356 ms-
Show 10 older checks
31 h agoExpected HTTP 402, got 400400490 ms-
36 h agoExpected HTTP 402, got 400400432 ms-
42 h agoExpected HTTP 402, got 400400217 ms-
47 h agoExpected HTTP 402, got 400400339 ms-
2 days agoExpected HTTP 402, got 400400406 ms-
2 days agoExpected HTTP 402, got 400400387 ms-
3 days agoExpected HTTP 402, got 400400375 ms-
3 days agoExpected HTTP 402, got 400400282 ms-
3 days agoExpected HTTP 402, got 400400608 ms-
3 days agoExpected HTTP 402, got 400400432 ms-