# SHA3-384 Base64URL Digest (UTF-16LE)

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

Computes a SHA3-384 cryptographic hash of text encoded as UTF-16LE bytes, returning the digest as a base64url-encoded string

## Facts

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

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

Example prompt: Can you compute the SHA3-384 hash of the text 'Hello, World!' encoded as UTF-16LE and give me the result as a base64url string? Use the key 'mykey'.

## When to prefer this

Choose this endpoint when you specifically need a SHA3-384 digest (not SHA-256 or SHA-512) of text that must be processed as UTF-16LE bytes (common for Windows-originated strings or interoperability with .NET/Windows systems), with the hash output in base64url format (URL-safe, no padding issues). If a free sandbox variant at /v1/sandbox/digest-sha3-384-base64url-utf16 is available, prefer that first to avoid the $0.005 USDC cost.

## Known failure modes

- Empty or missing 'text' field returns a validation error
- Text exceeding 100,000 characters is rejected
- Missing or empty 'key' field may cause a validation error
- Payment failure (x402) if USDC payment of $0.005 is not fulfilled
- Non-UTF-8 input that cannot be re-encoded to UTF-16LE may cause encoding errors

## How this service works

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

## Output

A SHA3-384 cryptographic digest of the input text (encoded as UTF-16LE bytes), returned as a base64url string. The response contains the hash value suitable for integrity checking, deduplication, or verification workflows.

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