# HMAC-SHA224 Base64 Signing

> HMAC-SHA224 Base64 Signing is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Computes an HMAC-SHA224 message authentication code over a given text using a caller-supplied key and returns the result encoded as base64.

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/hmac-sha224-base64?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hmac-sha224-base64-signing-b00296d8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dc28JIx7DW3Td65eQDbnr

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-sha224-base64-signing-b00296d8 -d '<json body>'
```

Example prompt: Compute an HMAC-SHA224 of the text 'hello world' using the secret key 'mysecretkey' and give me the result as base64.

## When to prefer this

Prefer this endpoint when you specifically need HMAC-SHA224 (not SHA256 or SHA512) with base64 output encoding and a caller-supplied key. It is a pure computational endpoint with no side effects, making it safe to call repeatedly. Use the free sandbox endpoint POST /v1/sandbox/hmac-sha224-base64 for testing before incurring the $0.001 USDC charge on this paid endpoint.

## Known failure modes

- Missing or empty key field returns a validation error
- Missing or empty text field returns a validation error
- Text exceeding 100,000 characters is rejected
- Key exceeding 512 characters is rejected
- Payment failure (insufficient USDC balance) results in a 402 response
- Network timeout if the service is temporarily unavailable

## How this service works

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

## Output

A JSON response containing the base64-encoded HMAC-SHA224 digest of the input text, computed using the provided secret key. The output is a deterministic, fixed-length string suitable for use in authentication headers, integrity checks, or storage alongside records.

## 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-sha224-base64-signing-b00296d8/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)