# Agent Forge Human-Readable Bytes Formatter

> Agent Forge Human-Readable Bytes Formatter is a paid API for AI agents from agent-forge.annushka1190.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Converts a raw byte count into a human-readable string (e.g. '1.23 MB') using standard binary or decimal units

## Facts

- Endpoint: POST https://agent-forge.annushka1190.workers.dev/v1/bytes
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-forge-human-readable-bytes-formatter-f0d8272e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BJUOQacqH5y5OGNNxW9r2

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-forge-human-readable-bytes-formatter-f0d8272e -d '<json body>'
```

Example prompt: Convert 15728640 bytes into a human-readable size string — like '15 MB' or whatever the appropriate unit is.

## When to prefer this

Choose this endpoint when you need a pay-per-request, no-account, no-API-key utility to format byte counts into human-readable strings — especially in autonomous agent workflows where provisioning credentials is impractical. Ideal for one-off conversions billed via x402 USDC micropayments.

## Known failure modes

- Missing or invalid 'input' body causes a 400-level error
- Non-numeric byte value results in a parse error
- Payment not attached or insufficient USDC causes a 402 Payment Required response
- Malformed JSON body returns a schema validation error

## How this service works

Hash and unit utilities for AI agents: SHA-256, SHA-1, HMAC-SHA256, stable JSON fingerprint, ETH/Gwei/Wei conversion, human bytes, and duration parsing. Pay-per-request USDC via x402. No API keys, no accounts.

## Output

Returns a JSON object with ok: true and a human-readable string representation of the input byte count using appropriate units (B, KB, MB, GB, TB), suitable for display in user interfaces or logs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "const": "json"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-forge-human-readable-bytes-formatter-f0d8272e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-forge.annushka1190.workers.dev](https://www.zero.xyz/host/agent-forge.annushka1190.workers.dev/llms.txt)