# SHA-512/224 Digest — Base64URL + UTF-16LE Encoding

> SHA-512/224 Digest — Base64URL + UTF-16LE Encoding is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.007/call, status unknown (last checked 2026-10-15).

Computes a SHA-512/224 hash of text encoded as UTF-16LE bytes, returning the digest as a base64url string

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-sha512-224-base64url-utf16?utm_source=zero.xyz
- Price: $0.007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sha-512-224-digest-base64url-utf-16le-encoding-e8e33665
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oJDUl3pUloEQFevREq3vN

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-224-digest-base64url-utf-16le-encoding-e8e33665 -d '<json body>'
```

Example prompt: Hash the text 'Hello, World!' using SHA-512/224 with UTF-16LE byte encoding and give me the result as a base64url digest string.

## When to prefer this

Choose this endpoint when you specifically need a SHA-512/224 hash (not SHA-256 or SHA-512) with UTF-16LE byte encoding and base64url output encoding — a combination common in Windows-ecosystem compatibility, certain token-generation schemes, or when an existing system already uses this exact algorithm and encoding triple. If you only need a generic hash or a different encoding (e.g. hex, base64 standard), a different endpoint is more appropriate.

## Known failure modes

- Text or key field missing or empty — validation error returned
- Text exceeds 100,000 character limit — request rejected
- Key string exceeds 512 character limit — request rejected
- Payment of $0.007 USDC not provided or declined — 402 response
- Malformed JSON body — parse error returned

## How this service works

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

## Output

Returns a base64url-encoded SHA-512/224 digest of the input text treated as UTF-16LE bytes. The output is a compact, URL-safe cryptographic hash string suitable for integrity checks, deduplication keys, or content identifiers.

## 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-224-digest-base64url-utf-16le-encoding-e8e33665/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)