Back to Browse
TextKit Human-Readable Byte Size Formatter
x402
TextKit Human-Readable Byte Size Formatter is a paid API for AI agents from textkit.johnaio281.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-22).
Converts a raw byte count into a human-readable string with appropriate units (KB, MB, GB, etc.)
Price / call$0.003
Success—
StatusUnknown
How this service works
General-purpose text, Unicode and date utilities for AI agents: homoglyph folding and spoofed-domain detection, Unicode script detection, NFC/NFD normalization, grapheme counting, date description (weekday, ISO week, quarter, leap year), business-day counting, slugify, FNV-1a hashing, Shannon entropy, string format detection (uuid, email, url, ipv4, jwt, iban), byte-encoding detection and human-readable byte sizes. Pay per request in USDC on Base via x402 - no signup, no API key, no KYC.
Output
A JSON object containing the original byte count, a human-readable string (e.g. '1 MB'), the value in kilobytes, and the value in mebibytes — ready to display directly to end users.
Example use cases
Display upload file size
“A user just uploaded a file that's 2097152 bytes — can you show me that in a friendly readable format like MB?”
Format disk usage report
“I have a storage report showing 107374182400 bytes used — convert that to a human-readable size like GB or TB for the dashboard.”
Show download size to user
“This download is 524288 bytes, what should I show the user — like '512 KB' or something readable?”
Technical details
Endpoint
GEThttps://textkit.johnaio281.workers.dev/api/tk/human-bytes?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a quick, pay-per-use, no-signup conversion of raw byte counts to human-readable sizes — especially useful in AI agent pipelines that handle file uploads, storage reporting, or any context where displaying raw bytes to end users is undesirable. Prefer this over building custom formatting logic when operating in a serverless or agent context that already uses x402 micropayments on Base.
Side effects
- Missing required 'bytes' query parameter returns an error
- Non-numeric or negative byte value may return an error or unexpected result
- Payment failure via x402 protocol blocks the request
- Very large integers beyond JavaScript safe integer range may produce inaccurate results
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"bytes": 1048576,
"readable": "1 MB",
"kilobytes": 1024,
"mebibytes": 1
}
}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"