Back to Browse
FastX402 Byte Size Parser
x402
FastX402 Byte Size Parser is a paid API for AI agents from fastx402.tools, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-17).
Parses a human-readable byte size string (e.g. '1.5 MiB', '800 KB') and returns its canonical SI and IEC representations along with the exact byte count.
Price / call$0.001
Success—
StatusUnknown
How this service works
146 pay-per-call tools for AI agents, from $0.001 per request in USDC on Base or Solana with x402. No account, no API key.
Output
Returns a JSON object with: `bytes` (exact integer byte count), `si` (SI-formatted string, e.g. '1.573 MB'), `iec` (IEC-formatted string, e.g. '1.5 MiB'), `unit` (detected unit, e.g. 'MiB'), `system` (detected system, 'SI' or 'IEC'), and `input` (the original input string).
Example use cases
Normalizing file sizes from user input
“A user typed '2.3 GiB' as an upload limit — can you parse that into an exact byte count and give me both the SI (GB) and IEC (GiB) representations?”
Storage quota comparison across systems
“I have two systems reporting sizes differently: one says '1.5 TB' and another says '1.4 TiB' — parse both and tell me the exact byte counts so I can compare them.”
Validating size strings in a data pipeline
“My pipeline received the string '500 MB' from a user config — parse it into bytes and confirm whether it's using SI or IEC units so I can apply the right conversion downstream.”
Technical details
Endpoint
GEThttps://fastx402.tools/byte-size-parse?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need to programmatically parse a human-readable byte size string into an exact integer byte count and get both SI and IEC canonical representations. It handles ambiguous unit prefixes (KB vs KiB, MB vs MiB) correctly, making it ideal for data pipelines, storage quota systems, or any agent that receives user-supplied file size strings and needs normalized, unambiguous values.
Side effects
- Missing `size` query parameter returns an error
- Unrecognized unit suffix (e.g. 'ZZB') causes a parse failure
- Negative or zero values may be rejected
- Extremely large numbers beyond supported range may fail
- Malformed input like '1.5 MBKB' returns an error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"si": "1.573 MB",
"iec": "1.5 MiB",
"unit": "MiB",
"bytes": 1572864,
"input": "1.5 MiB",
"system": "IEC"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"