Monitor Latency
by latency-probe-bulk in Developer tools
Bulk latency probe: up to 20 urls in one call, processed concurrently, results returned in input order with a per-item error field and a count of failures. Same answer per item as the single /monitor/latency endpoint (Latency probe). Batch enrichment for agents that hold a list. $0.01 per batch.
https://intel.rallylive.ca/bulk/monitor/latency- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 53 ms
- 529 ms slowest 5%
- Last check
- Passed
- 8 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://intel.rallylive.ca/bulk/monitor/latency
Each call costs $0.01 in USDC on Base Sepolia, 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://intel.rallylive.ca/bulk/monitor/latency?urls=https%3A%2F%2Fgithub.com%2F%2C+https%3A%2F%2Fexample.com%2F%2C+https%3A%2F%2Fwww.iana.org%2FExample response
The provider's example. We can't check it without paying.
Example response, 34 lines
{
"count": 2,
"failed": 0,
"results": [
{
"input": "https://example.com/",
"result": {
"avg_ms": 106,
"bytes": 1256,
"jitter_ms": 22,
"max_ms": 120,
"min_ms": 98,
"samples_ms": [
120,
98,
101
],
"server": "ECAcc",
"status": [
200,
200,
200
],
"url": "https://example.com/"
}
},
{
"input": "…",
"result": {
"…": "…"
}
}
]
}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://intel.rallylive.ca/bulk/monitor/latency?urls=https%3A%2F%2Fgithub.com%2F%2C+https%3A%2F%2Fexample.com%2F%2C+https%3A%2F%2Fwww.iana.org%2F'
# 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://intel.rallylive.ca/bulk/monitor/latency?urls=https%3A%2F%2Fgithub.com%2F%2C+https%3A%2F%2Fexample.com%2F%2C+https%3A%2F%2Fwww.iana.org%2F' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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%2Fintel.rallylive.ca%2Fbulk%2Fmonitor%2Flatency
const res = await pay("https://intel.rallylive.ca/bulk/monitor/latency?urls=https%3A%2F%2Fgithub.com%2F%2C+https%3A%2F%2Fexample.com%2F%2C+https%3A%2F%2Fwww.iana.org%2F");
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://intel.rallylive.ca/bulk/monitor/latency?urls=https%3A%2F%2Fgithub.com%2F%2C+https%3A%2F%2Fexample.com%2F%2C+https%3A%2F%2Fwww.iana.org%2F")
print(res.status_code, res.text)Security scan
1 finding
- Payment address changed recently in payment
Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 8 h ago | Passed | 402 | 44 ms | $0.01 |
| 19 h ago | Passed | 402 | 529 ms | $0.01 |
| 29 h ago | Passed | 402 | 84 ms | $0.01 |
| 39 h ago | Passed | 402 | 374 ms | $0.01 |
| 2 days ago | Passed | 402 | 58 ms | $0.01 |
Show 10 older checks
| 2 days ago | Passed | 402 | 49 ms | $0.01 |
| 2 days ago | Passed | 402 | 44 ms | $0.01 |
| 3 days ago | Passed | 402 | 74 ms | $0.01 |
| 3 days ago | Passed | 402 | 100 ms | $0.01 |
| 3 days ago | Passed | 402 | 52 ms | $0.01 |
| 3 days ago | Passed | 402 | 53 ms | $0.01 |
| 3 days ago | Passed | 402 | 53 ms | $0.01 |
| 3 days ago | Passed | 402 | 43 ms | $0.01 |
| 4 days ago | Passed | 402 | 40 ms | $0.01 |
| 4 days ago | Passed | 402 | 49 ms | $0.01 |
History
| 11 Oct 2026 | Payment address changed from 0x91D568599fB802Cb3f03F067D2063785dBAF0abd to 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3 |