33trust / 100

Throughput Budget

by Systems Capacity Calculators in Other

x402 APIFailing, checked 24 h ago

Requests per second times payload size to Mbps with peak factor, protocol overhead and link headroom; or IOPS to MB/s.

GET
https://data-calc.x402tookit.com/throughput-budget
Price
$0.02
per call in USDC
Uptime
53.9%
last 30 days
Response time
513 ms
555 ms slowest 5%
Last check
Failed
24 h ago, next in 51 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 24 h ago: Expected HTTP 402, got 530

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

How to call it

GET https://data-calc.x402tookit.com/throughput-budget

Each call costs $0.02 in USDC on Polygon, 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://data-calc.x402tookit.com/throughput-budget?bytesPerRequest=100000&peakFactor=2&requestsPerSecond=1000

Parameters

ParameterTypeRequiredDescription
bytesPerRequestnumberYesAverage payload size per request in bytes (a 4 KiB block = 4096), 1 to 1e12
linkMbpsnumberNoOptional existing link capacity in Mbps, to check fit
overheadPercentnumberNoProtocol overhead added to the payload, percent (default 0; TCP/IP/Ethernet is about 5 to 10)
peakFactornumberNoPeak-to-average ratio (default 1)
requestsPerSecondnumberYesAverage requests (or I/O operations) per second, 0.001 to 1e9
targetUtilizationPercentnumberNoHighest sustained link utilisation you accept, 10 to 100 (default 70)

Example response

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

Example response, 27 lines
{
  "asOf": "2026-10-11T20:19:41.023Z",
  "averageMBps": 100,
  "averageMbps": 800,
  "averageMiBps": 95.367,
  "dataPerDayGB": 8640,
  "dataPerMonthTB": 259.2,
  "degraded": false,
  "disclaimer": "Screening signal computed from the named public source. Not financial, legal or investment advice; provided as is. Verify at the source before acting.",
  "notChecked": [
    "compression, caching and CDN offload, which cut real traffic",
    "response versus request direction (give the larger direction)",
    "…2 more"
  ],
  "peakMbps": 1600,
  "provisionedMbps": 2285.714,
  "reasons": [
    "Mbps = requests/s x bytes x 8 x (1 + overhead) / 10^6 (decimal megabits).",
    "Provisioned = peak / target utilisation: a link running hot adds queueing delay, so leave headroom.",
    "…1 more"
  ],
  "source": "computed locally",
  "suggestedLink": "10 Gbps",
  "summary": "1000 req/s x 100000 bytes = 800 Mbps average, 1600 Mbps at peak x2; provision about 2285.714 Mbps to stay under 70% utilisation (10 Gbps class).",
  "targetUtilizationPercent": 70,
  "verdict": "SIZED"
}

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 'https://data-calc.x402tookit.com/throughput-budget?bytesPerRequest=100000&peakFactor=2&requestsPerSecond=1000'

# 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://data-calc.x402tookit.com/throughput-budget?bytesPerRequest=100000&peakFactor=2&requestsPerSecond=1000' \
  | 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%2Fdata-calc.x402tookit.com%2Fthroughput-budget
const res = await pay("https://data-calc.x402tookit.com/throughput-budget?bytesPerRequest=100000&peakFactor=2&requestsPerSecond=1000");
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.get("https://data-calc.x402tookit.com/throughput-budget?bytesPerRequest=100000&peakFactor=2&requestsPerSecond=1000")
    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
24 h agoExpected HTTP 402, got 530530114 ms-
2 days agoExpected HTTP 402, got 530530132 ms-
3 days agoExpected HTTP 402, got 530530114 ms-
5 days agoExpected HTTP 402, got 53053093 ms-
5 days agoExpected HTTP 402, got 530530253 ms-
Show 8 older checks
5 days agoExpected HTTP 402, got 530530223 ms-
5 days agoPassed402548 ms$0.02
6 days agoPassed402513 ms$0.02
6 days agoPassed402525 ms$0.02
6 days agoPassed402555 ms$0.02
6 days agoPassed402494 ms$0.02
6 days agoPassed402510 ms$0.02
7 days agoPassed402491 ms$0.02