# SHA3-384 Digest Base64url Encoder

> SHA3-384 Digest Base64url Encoder is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.009/call, status unknown (last checked 2026-10-01).

Computes a SHA3-384 cryptographic hash of input text and returns the digest encoded as a base64url string

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-sha3-384-base64url?utm_source=zero.xyz
- Price: $0.009/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sha3-384-digest-base64url-encoder-28161953
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1LmBMVxon2etZbh1i_Czh

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-digest-base64url-encoder-28161953 -d '<json body>'
```

Example prompt: Can you compute the SHA3-384 hash of the text 'Hello, world! This is my message.' and give me the result in base64url encoding?

## When to prefer this

Choose this endpoint when you specifically need a SHA3-384 digest encoded in base64url format (URL-safe, no padding characters). Prefer this over SHA3-256 when longer digest length (384 bits) is required for higher collision resistance. Use base64url encoding when the hash will be embedded in URLs, JWT headers, or filenames. If cost is a concern, try the free sandbox endpoint POST /v1/sandbox/digest-sha3-384-base64url first. Use sibling endpoints for different algorithms (SHA3-256, SHA3-512) or encodings (base64, base32, hex).

## Known failure modes

- Input text exceeds 100,000 character limit — request rejected
- Key parameter exceeds 512 character limit — request rejected
- Empty or missing text field — validation error
- Payment not provided or insufficient USDC — 402 response
- Malformed JSON body — 400 bad request

## How this service works

Call when an agent needs a sha3-384 digest of text, encoded as base64url. No network and no LLM. Exact $0.009 USDC. Prefer unpaid POST /v1/sandbox/digest-sha3-384-base64url first.

## Output

A base64url-encoded string representing the SHA3-384 cryptographic digest of the input text. The hash is deterministic, produces no side effects, and requires no network calls or LLM inference — purely a cryptographic computation.

## 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-digest-base64url-encoder-28161953/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)