# MD5 Digest of UTF-16LE Text, Base64URL-Encoded

> MD5 Digest of UTF-16LE Text, Base64URL-Encoded 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-02).

Computes an MD5 hash of a text string encoded as UTF-16LE bytes, then returns the result as a base64url string

## Facts

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

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 md5-digest-of-utf-16le-text-base64url-encoded-1f8a366a -d '<json body>'
```

Example prompt: Compute the MD5 hash of the text 'Hello, World!' treating it as UTF-16LE bytes and give me the result as a base64url string.

## When to prefer this

Use this endpoint when you specifically need an MD5 hash computed over UTF-16LE byte representation of a string with base64url output encoding — common in legacy Windows/Microsoft compatibility scenarios, certain HMAC-like keyed digest flows, or when a downstream system mandates this exact combination of encoding and hash format. Prefer the free sandbox endpoint (/v1/sandbox/digest-md5-base64url-utf16) for testing before using this paid version.

## Known failure modes

- Missing or empty 'text' field returns a validation error
- Text exceeding 100,000 characters is rejected
- Missing or empty 'key' field may be required and returns an error if absent
- Payment not provided or insufficient USDC results in a 402 response
- Malformed JSON body returns a 400 error

## How this service works

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

## Output

A base64url-encoded string representing the MD5 hash of the input text converted to UTF-16LE bytes. The result is URL-safe and compact, suitable for use in headers, cache keys, or integrity checks.

## 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/md5-digest-of-utf-16le-text-base64url-encoded-1f8a366a/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)