# SHA3-256 Hex Digest (UTF-16LE)

> SHA3-256 Hex Digest (UTF-16LE) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.007/call, status unknown (last checked 2026-09-29).

Computes a SHA3-256 hash of input text encoded as UTF-16LE bytes, returned as a lowercase hex string.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-sha3-256-hex-utf16?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sha3-256-hex-digest-utf-16le-edf8ce9f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ie9P9PSPZZE47KW5CXBui

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 sha3-256-hex-digest-utf-16le-edf8ce9f -d '<json body>'
```

Example prompt: Can you compute the SHA3-256 hash of 'Hello, World!' encoded as UTF-16LE bytes and give me the result as a hex string?

## When to prefer this

Choose this endpoint when you specifically need a SHA3-256 hash computed over UTF-16LE byte encoding of the input (as opposed to UTF-8), and need the result as a hex string. This is especially relevant when interoperating with systems that use UTF-16LE encoding conventions (e.g., Windows-native applications, certain .NET or legacy Microsoft systems). Prefer the unpaid sandbox version (/v1/sandbox/digest-sha3-256-hex-utf16) for testing or cost-sensitive workflows. Do not use this if you need SHA-256 (not SHA3), or if UTF-8 encoding is sufficient.

## Known failure modes

- Empty or missing 'text' field returns a validation error
- Text exceeding 100,000 characters is rejected
- Invalid or missing content-type header may cause parsing failure
- Network timeout or service unavailability returns a 5xx error
- Incorrect payment or missing x402 payment header results in a 402 Payment Required response

## How this service works

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

## Output

A hex-encoded SHA3-256 digest string computed over the UTF-16LE byte representation of the input text. The response is a deterministic, fixed-length lowercase hexadecimal string (64 characters).

## 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/sha3-256-hex-digest-utf-16le-edf8ce9f/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)