78trust / 100

Http Latency

by HTTP Latency Check API in Developer tools

x402 APIPassing, checked 50 min ago

HTTP Latency Check API. Measure HTTP response latency for a URL from the Cloudflare Worker edge. Returns status code, latency, redirect, content type and edge location metadata. Useful for uptime checks, API diagnostics and website monitoring. Paid per call via x402.

POST
https://tools.ipintel.ai/http-latency
Price
$0.001
per call in USDC
Uptime
95.7%
last 30 days
Response time
746 ms
944 ms slowest 5%
Last check
Passed
50 min ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

POST https://tools.ipintel.ai/http-latency

Each call costs $0.001 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://tools.ipintel.ai/http-latency
content-type: application/json

{
  "url": "https://example.com"
}

Parameters

ParameterTypeRequiredDescription
methodstringNoHTTP method to use. Defaults to HEAD. One of: HEAD, GET.
urlstringYesHTTP or HTTPS URL to check

Example response

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

{
  "from": {
    "colo": "SOF",
    "country": "BG",
    "network": "cloudflare_worker"
  },
  "latency_ms": 123,
  "method": "HEAD",
  "ok": true,
  "redirect_location": null,
  "service": "http_latency",
  "status_code": 200,
  "timestamp": "2026-06-23T00:00:00.000Z",
  "url": "https://example.com"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://tools.ipintel.ai/http-latency' \
  -H 'content-type: application/json' \
  --data-raw '{"url":"https://example.com"}'

# 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://tools.ipintel.ai/http-latency' \
  -H 'content-type: application/json' \
  --data-raw '{"url":"https://example.com"}' \
  | 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.001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.001" });
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.001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Ftools.ipintel.ai%2Fhttp-latency&method=POST
const res = await pay("https://tools.ipintel.ai/http-latency", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "url": "https://example.com"
  }),
});
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.001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://tools.ipintel.ai/http-latency",
        json={
            "url": "https://example.com",
        },
    )
    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 agoPassed402483 ms$0.001
5 h agoPassed402631 ms$0.001
9 h agoPassed402761 ms$0.001
13 h agoPassed4021.1 s$0.001
17 h agoPassed402858 ms$0.001
Show 10 older checks
21 h agoPassed402722 ms$0.001
25 h agoPassed402663 ms$0.001
29 h agoPassed402895 ms$0.001
33 h agoPassed402866 ms$0.001
37 h agoPassed402746 ms$0.001
40 h agoPassed402589 ms$0.001
44 h agoPassed402789 ms$0.001
47 h agoTimed out---
2 days agoPassed402698 ms$0.001
2 days agoPassed402655 ms$0.001