77trust / 100

Chain Network

by HubVibe in Onchain & crypto

x402 APIPassing, checked 50 min ago

Base network status and gas price: current block height and gas price (wei and gwei), live from a Base mainnet RPC node. Use it to check Base is moving, time an on-chain action or estimate gas before sending a transaction. Keyless, pay per call. No input needed.

POST https://hubvibe-io.com/work/chain/network

Last 30 days

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

Uptime
100%
Response time
377 ms typical, 432 ms slowest 5%
Last check
50 min ago
Next check
any minute now

How to call it

POST https://hubvibe-io.com/work/chain/network

Each call costs $0.02 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.

POST https://hubvibe-io.com/work/chain/network
content-type: application/json

{}

Parameters

ParameterTypeRequiredDescription
languagestringNo

Example response

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

Example response, 28 lines
{
  "price_usd": 0.02,
  "provenance": {
    "attempts": 1,
    "elapsed_ms": 660,
    "providers_used": [
      "base_rpc"
    ],
    "steps": [
      {
        "ms": 640,
        "ok": true,
        "provider": "base_rpc",
        "step": "network"
      }
    ]
  },
  "receipt_id": "rcpt_9f1c2b3a4d5e6f70",
  "receipt_url": "/work/receipts/rcpt_9f1c2b3a4d5e6f70",
  "result": {
    "block_number": 41230577,
    "gas_price_gwei": 0.0125,
    "gas_price_wei": "12500000",
    "network": "base-mainnet"
  },
  "status": "ok",
  "worker": "chain.network"
}

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.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://hubvibe-io.com/work/chain/network' \
  -H 'content-type: application/json' \
  --data-raw '{}'

# 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 - -X POST 'https://hubvibe-io.com/work/chain/network' \
  -H 'content-type: application/json' \
  --data-raw '{}' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fhubvibe-io.com%2Fwork%2Fchain%2Fnetwork&method=POST
const res = await pay("https://hubvibe-io.com/work/chain/network", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({}),
});
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://hubvibe-io.com/work/chain/network",
        json={},
    )
    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
50 min agoPassed402351 ms$0.02
5 h agoPassed402393 ms$0.02
9 h agoPassed402432 ms$0.02
13 h agoPassed402364 ms$0.02
16 h agoPassed402359 ms$0.02
20 h agoPassed402364 ms$0.02
24 h agoPassed402424 ms$0.02
27 h agoPassed402387 ms$0.02
31 h agoPassed402119 ms$0.02
35 h agoPassed402420 ms$0.02
38 h agoPassed402591 ms$0.02
42 h agoPassed402379 ms$0.02
45 h agoPassed402402 ms$0.02
2 days agoPassed402358 ms$0.02
2 days agoPassed402358 ms$0.02