# HMAC-SHA384 Base64url Signer

> HMAC-SHA384 Base64url Signer 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 an HMAC-SHA384 digest of text using a caller-supplied key and returns it encoded as base64url

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/hmac-sha384-base64url?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/hmac-sha384-base64url-signer-68d3e65d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jEKmeA8VaRtfMNaIvPyAB

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 hmac-sha384-base64url-signer-68d3e65d -d '<json body>'
```

Example prompt: Compute an HMAC-SHA384 signature of the text 'order:12345:confirmed' using the secret key 'mySecretKey2024' and give me the result as base64url.

## When to prefer this

Choose this endpoint when you need an HMAC-SHA384 digest specifically encoded as base64url (URL-safe, no padding issues), rather than hex or standard base64. Prefer this over HMAC-SHA512 variants when the receiving system expects SHA384. Use the free sandbox endpoint (/v1/sandbox/hmac-sha384-base64url) during development to avoid costs; switch to this paid endpoint in production workflows requiring guaranteed compute.

## Known failure modes

- Empty or missing 'key' field returns a validation error
- Empty or missing 'text' field returns a validation error
- Text exceeding 100,000 characters is rejected
- Key exceeding 512 characters is rejected
- Payment failure results in a 402 response; use the sandbox endpoint first to verify behavior
- Malformed JSON body returns a 400 error

## How this service works

Call when an agent needs an HMAC-sha384 of text with a caller-supplied key, encoded as base64url. Exact $0.01 USDC. Prefer unpaid POST /v1/sandbox/hmac-sha384-base64url first.

## Output

A base64url-encoded string representing the HMAC-SHA384 digest of the provided text, computed with the supplied key. The response contains the signature ready to be embedded in headers, tokens, or integrity checks.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "examples": [
    "secret"
   ],
   "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/hmac-sha384-base64url-signer-68d3e65d/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)