# Keyronne Cryptographic Hash & HMAC API

> Keyronne Cryptographic Hash & HMAC API is a paid API for AI agents from keyronne.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Computes cryptographic digests (MD5, SHA-1, SHA-256, SHA-384, SHA-512) and HMACs over input text, returning results as hex, base64, or base64url.

## Facts

- Endpoint: POST https://keyronne.com/api/hash
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/keyronne-cryptographic-hash-hmac-api-70d3d456
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4utfXFxtDnH2vvJ0QqYzZ

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 keyronne-cryptographic-hash-hmac-api-70d3d456 -d '<json body>'
```

Example prompt: Compute a SHA-256 hash of the string 'hello world' and give me the result as hex.

## When to prefer this

Use this endpoint when you need deterministic, server-side cryptographic hashing without running local code — ideal for agents that need checksums, content fingerprints, HMAC signatures, or hash-based verification and cannot execute native crypto libraries. Prefer over alternatives when HMAC with a secret key is needed or when multiple algorithms and output encodings must be supported in a single unified API.

## Known failure modes

- Unsupported algorithm value returns validation error
- Invalid encoding enum value returns error
- Missing 'text' field returns 400 bad request
- Key provided but algorithm not supported for HMAC returns error
- Payment not fulfilled returns 402 Payment Required

## How this service works

Compute cryptographic digests and HMACs deterministically: MD5, SHA-1, SHA-256, SHA-384, SHA-512, output as hex, base64, or base64url. Add a "key" for HMAC. Built for checksums, content addressing, and signature verification. Inputs are hashed and discarded. POST a JSON body like: {"text":"hello world","algorithm":"sha256","encoding":"hex"}

## Output

Returns the computed hash or HMAC as a string in the requested encoding (hex, base64, or base64url). The input text is discarded after hashing and never stored.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "description": "If present, compute HMAC-<algorithm> with this key instead of a plain hash."
  },
  "text": {
   "type": "string",
   "description": "The data to hash."
  },
  "encoding": {
   "enum": [
    "hex",
    "base64",
    "base64url"
   ],
   "type": "string",
   "default": "hex"
  },
  "algorithm": {
   "enum": [
    "md5",
    "sha1",
    "sha256",
    "sha384",
    "sha512"
   ],
   "type": "string",
   "default": "sha256"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keyronne-cryptographic-hash-hmac-api-70d3d456/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from keyronne.com](https://www.zero.xyz/host/keyronne.com/llms.txt)