# SHA3-256 Digest (UTF-16LE → Base64URL)

> SHA3-256 Digest (UTF-16LE → Base64URL) is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-24).

Computes a SHA3-256 hash of text encoded as UTF-16LE bytes and returns the digest as a base64url-encoded string.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-sha3-256-base64url-utf16?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sha3-256-digest-utf-16le-base64url-86116695
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LT_K7nTv-lPDXQnXPM43n

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

Example prompt: Can you compute a SHA3-256 hash of the text 'Hello, World!' using UTF-16LE encoding and give me the result as a base64url string? The key is 'my-request-key'.

## When to prefer this

Choose this endpoint when you specifically need a SHA3-256 hash with UTF-16LE byte encoding and base64url output format — for example, when interfacing with systems that use Windows-style UTF-16LE text encoding or when a downstream system expects base64url-encoded SHA3-256 digests. Prefer the free sandbox endpoint (/v1/sandbox/digest-sha3-256-base64url-utf16) for testing. Use sibling endpoints on the same host if you need a different hash algorithm, character encoding (e.g. latin1), or output encoding (e.g. hex, base32).

## Known failure modes

- Text exceeds 100,000 character limit — request rejected
- Key field is empty or missing — validation error
- Text field is empty or missing — validation error
- Payment of $0.003 USDC not provided — HTTP 402 returned
- Text contains characters that cause UTF-16LE encoding issues

## How this service works

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

## Output

Returns a SHA3-256 cryptographic digest of the input text (interpreted as UTF-16LE bytes), encoded as a base64url string. The response is deterministic for any given input text.

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