# Blake2s-256 Hex-to-Base64 Digest

> Blake2s-256 Hex-to-Base64 Digest is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Computes a BLAKE2s-256 digest of hex-encoded bytes and returns the result encoded as base64

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/digest-blake2s256-base64-rawhex?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blake2s-256-hex-to-base64-digest-4359d94f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6lhthoakU4tsknvMgshMf

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 blake2s-256-hex-to-base64-digest-4359d94f -d '<json body>'
```

Example prompt: Can you compute the BLAKE2s-256 hash of these hex bytes '48656c6c6f' and give me the result as base64? Use the key 'mysecretkey'.

## When to prefer this

Choose this endpoint when you specifically need a BLAKE2s-256 hash (not SHA-256, BLAKE2b, or MD5) of hex-encoded binary data with the output encoded as base64. It is ideal for cryptographic fingerprinting, data integrity checks, or protocol-level message signing where BLAKE2s is the required algorithm. Prefer the free sandbox endpoint (/v1/sandbox/digest-blake2s256-base64-rawhex) first if available; use this paid endpoint when the sandbox is unavailable or rate-limited.

## Known failure modes

- Invalid hex string input (non-hex characters) — likely returns a 4xx error
- Input text or key exceeds maximum length (100,000 and 512 chars respectively) — request rejected
- Payment not processed correctly — 402 response requiring USDC payment
- Malformed request body — 400 bad request
- Service unavailable — 5xx error from upstream

## How this service works

Call when an agent needs a blake2s256 digest of hex bytes, encoded as base64. Exact $0.01 USDC. Prefer unpaid POST /v1/sandbox/digest-blake2s256-base64-rawhex first.

## Output

Returns a base64-encoded BLAKE2s-256 digest of the input hex bytes, optionally keyed with the provided key string. The response is a compact cryptographic hash suitable for integrity verification or fingerprinting.

## 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": [
    "68656c6c6f"
   ],
   "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/blake2s-256-hex-to-base64-digest-4359d94f/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)
