# HMAC-SHA384 Hex Digest

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

Computes an HMAC-SHA384 message authentication code for a given text using a caller-supplied key, returning the result as a lowercase hex string.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/hmac-sha384-hex?utm_source=zero.xyz
- Price: $0.008/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-hex-digest-0c9fe772
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TKAlPU0at6uS07juzPAdf

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-hex-digest-0c9fe772 -d '<json body>'
```

Example prompt: Compute an HMAC-SHA384 hex digest of the text 'Hello, world!' using the secret key 'mysecretkey123'.

## When to prefer this

Choose this endpoint when an agent needs a server-side HMAC-SHA384 computation without implementing crypto locally, especially in sandboxed environments lacking native crypto libraries. Prefer the free sandbox variant POST /v1/sandbox/hmac-sha384-hex for testing before spending USDC. Use over SHA-256 HMAC alternatives when SHA-384 strength is specifically required by a downstream API or protocol.

## Known failure modes

- Empty or missing 'key' field returns a validation error
- Empty or missing 'text' field returns a validation error
- Key exceeding 512 characters is rejected
- Text exceeding 100,000 characters is rejected
- Payment of $0.008 USDC not provided or declined results in HTTP 402
- Network timeout if upstream service is unavailable

## How this service works

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

## Output

A hex-encoded HMAC-SHA384 digest string (96 hex characters) derived from the supplied text and key. The response confirms the cryptographic signature computed server-side with no additional metadata.

## 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-hex-digest-0c9fe772/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)