# SHA-512/256 Digest with Base32 Encoding (UTF-16LE)

> SHA-512/256 Digest with Base32 Encoding (UTF-16LE) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-19).

Computes a SHA-512/256 digest of text encoded as UTF-16LE bytes, then returns the result as a Base32 string

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-sha512-256-base32-utf16?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sha-512-256-digest-with-base32-encoding-utf-16le-11fa9601
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MslV1QYirt_ApfGhCfX_p

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 sha-512-256-digest-with-base32-encoding-utf-16le-11fa9601 -d '<json body>'
```

Example prompt: Hash the text 'Hello, World!' using SHA-512/256 over its UTF-16LE bytes and give me the result as a Base32 string.

## When to prefer this

Choose this endpoint when you specifically need a SHA-512/256 digest of text processed as UTF-16LE bytes and want the result in Base32 encoding — a combination commonly required for interoperability with Windows-native systems, certain cryptographic protocols, or external services that expect this precise encoding pipeline. If you only need a standard SHA-256 or SHA-512 hash in hex or base64, use a more common hashing endpoint instead.

## Known failure modes

- Missing or empty 'text' field returns a validation error
- Input text exceeding 100,000 characters is rejected
- Missing 'key' field may cause authentication or routing failure
- Payment not included or insufficient USDC results in HTTP 402
- Non-UTF-8 safe characters in input may cause unexpected encoding behavior

## How this service works

Call when an agent needs a sha512-256 digest of utf16le bytes, encoded as base32. Exact $0.002 USDC. Prefer unpaid POST /v1/sandbox/digest-sha512-256-base32-utf16 first.

## Output

A Base32-encoded string representing the SHA-512/256 digest of the input text after encoding it as UTF-16LE bytes. The result is a deterministic, fixed-length hash suitable for integrity checks, deduplication, or fingerprinting.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "maxLength": 512,
   "minLength": 1,
   "description": "HMAC secret. Required on HMAC SKUs. Omit it for plain digests and checksums. The key is not stored."
  },
  "text": {
   "type": "string",
   "examples": [
    "hello"
   ],
   "maxLength": 100000,
   "minLength": 1,
   "description": "Message to digest. For raw-hex SKUs this is hex bytes; for utf16 or latin1 SKUs it is decoded with that encoding. Otherwise it is UTF-8 text."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sha-512-256-digest-with-base32-encoding-utf-16le-11fa9601/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)