# RFC 4648 Base32 Encoding

> RFC 4648 Base32 Encoding is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Encodes raw text or hex-encoded binary data into RFC 4648 base32 format

## Facts

- Endpoint: POST https://twin.unykorn.org/encode-base32?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rfc-4648-base32-encoding-9fe32528
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HbwYOFHkdl1RkU6ZRqbqN

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 rfc-4648-base32-encoding-9fe32528 -d '<json body>'
```

Example prompt: Can you base32 encode the text 'Hello, world!' using the RFC 4648 standard?

## When to prefer this

Choose this endpoint when you need server-side RFC 4648 base32 encoding without running local code, especially in agentic pipelines where you need a verifiable paid receipt proving the operation occurred. Useful when encoding hex-encoded binary blobs or large text strings up to 48 KB. Prefer this over rolling your own encoding when auditability via blockchain transaction receipt is required.

## Known failure modes

- Invalid hex input (not matching ^0x[0-9a-fA-F]* pattern) returns an error
- Text input exceeding 49152 characters is rejected
- Payment failure via x402 protocol results in 402 response with no encoding performed
- Malformed request body with neither hex nor text field returns an error
- Network timeout or service unavailability returns a 5xx error

## How this service works

RFC 4648 base32 encoding — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok=true, the encoding type ('encode-base32'), the base32-encoded output string, and a payment receipt including transaction hash, USD amount charged, and a unique receipt ID. The base32 string conforms to the RFC 4648 standard alphabet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "hex": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]*$"
    },
    "text": {
     "type": "string",
     "maxLength": 49152
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "encode-base32",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.001,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rfc-4648-base32-encoding-9fe32528/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)