Raid Capacity
by Systems Capacity Calculators in Documents & files
RAID 0/1/5/6/10 and ZFS RAID-Z usable capacity, efficiency, fault tolerance, write penalty and rebuild read-error risk.
https://data-calc.x402tookit.com/raid-capacity- Price
- $0.02
- per call in USDC
- Uptime
- 64.3%
- last 30 days
- Response time
- 531 ms
- 1.0 s 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://data-calc.x402tookit.com/raid-capacity
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/raid-capacity?diskTb=4&disks=4&level=raid5Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
diskTb | number | Yes | Capacity of each disk in decimal terabytes (1 TB = 10^12 bytes), 0.001 to 1000 |
disks | integer | Yes | Number of disks in the array, 1 to 128 |
level | string | Yes | One of jbod, raid0, raid1, raid5, raid6, raid10, raidz1, raidz2, raidz3 |
spares | integer | No | Hot spares, not counted in capacity (default 0) |
ureBits | number | No | Unrecoverable read error rate as 1 error per this many bits read (default 1e14 consumer; enterprise 1e15) |
Example response
The provider's example. We can't check it without paying.
Example response, 36 lines
{
"asOf": "2026-10-11T20:19:40.243Z",
"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.",
"diskTb": 4,
"disks": 4,
"disksTotalInstalled": 4,
"efficiencyPercent": 75,
"faultTolerance": 1,
"faultToleranceBestCase": 1,
"label": "RAID 5 (single parity)",
"level": "raid5",
"notChecked": [
"filesystem and metadata overhead, ZFS slop space and reserved blocks (real usable space is a few percent lower)",
"performance beyond the textbook write penalty: controller, cache and workload dominate",
"…2 more"
],
"randomWritePenalty": 4,
"rawTb": 16,
"reasons": [
"With single redundancy, a read error during rebuild may mean data loss for the affected stripe (and an aborted rebuild on some controllers).",
"Capacity is in decimal terabytes as sold; operating systems that report TiB show about 9% less.",
"…1 more"
],
"rebuild": {
"probabilityOfReadError": 0.6171071140248879,
"terabytesRead": 12,
"ureOneErrorPerBits": 100000000000000
},
"source": "computed locally (RAID level definitions)",
"spares": 0,
"summary": "RAID 5 (single parity), 4 x 4 TB: 12.00 TB usable (10.91 TiB), 75.0% efficient, survives 1 disk failure. Rebuild reads 12 TB: 61.7% chance of an unrecoverable read error.",
"usableTb": 12,
"usableTiB": 10.9139,
"verdict": "REBUILD_RISK_HIGH"
}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/raid-capacity?diskTb=4&disks=4&level=raid5'
# 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/raid-capacity?diskTb=4&disks=4&level=raid5' \
| 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.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%2Fraid-capacity
const res = await pay("https://data-calc.x402tookit.com/raid-capacity?diskTb=4&disks=4&level=raid5");
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/raid-capacity?diskTb=4&disks=4&level=raid5")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 8 h ago | Passed | 402 | 510 ms | $0.02 |
| 21 h ago | Passed | 402 | 547 ms | $0.02 |
| 2 days ago | Expected HTTP 402, got 530 | 530 | 147 ms | - |
| 3 days ago | Expected HTTP 402, got 530 | 530 | 96 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 104 ms | - |
Show 9 older checks
| 5 days ago | Expected HTTP 402, got 530 | 530 | 185 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 202 ms | - |
| 5 days ago | Passed | 402 | 531 ms | $0.02 |
| 6 days ago | Passed | 402 | 526 ms | $0.02 |
| 6 days ago | Passed | 402 | 940 ms | $0.02 |
| 6 days ago | Passed | 402 | 606 ms | $0.02 |
| 6 days ago | Passed | 402 | 1.0 s | $0.02 |
| 6 days ago | Passed | 402 | 522 ms | $0.02 |
| 7 days ago | Passed | 402 | 420 ms | $0.02 |