# SHA-256 Hex Digest of UTF-16LE Encoded Text

> SHA-256 Hex Digest of UTF-16LE Encoded Text is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-02).

Computes a SHA-256 hash of input text encoded as UTF-16LE bytes and returns it as a lowercase hex string

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-sha256-hex-utf16?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sha-256-hex-digest-of-utf-16le-encoded-text-e244357c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_69DUNJAboiBHU1CJ9jSgM

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-256-hex-digest-of-utf-16le-encoded-text-e244357c -d '<json body>'
```

Example prompt: Can you compute the SHA-256 hex digest of the text 'Hello, World!' using UTF-16LE byte encoding?

## When to prefer this

Choose this endpoint when you specifically need a SHA-256 hash computed over UTF-16LE byte-encoded text, as is common in Windows-native, .NET, or legacy Microsoft ecosystem integrations. Use this instead of a generic SHA-256 endpoint when the encoding layer matters for interoperability — for example, when matching hashes produced by Windows CryptoAPI, PowerShell, or .NET's System.Text.Encoding.Unicode. The free sandbox endpoint (POST /v1/sandbox/digest-sha256-hex-utf16) should be tried first before using this paid version.

## Known failure modes

- Empty or missing 'text' field returns a validation error
- Text exceeding 100,000 characters is rejected
- Missing or empty 'key' field causes a request error
- Payment of exactly $0.005 USDC required; insufficient payment returns a 402 error
- Malformed JSON body returns a 400 error

## How this service works

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

## Output

Returns a lowercase hexadecimal string representing the SHA-256 digest of the input text after encoding it as UTF-16LE bytes. The output is a fixed-length 64-character hex string suitable for integrity checks, deduplication, or interoperability with systems that use UTF-16LE encoding conventions.

## 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-256-hex-digest-of-utf-16le-encoded-text-e244357c/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)