# MoneyTools HMAC Verify

> MoneyTools HMAC Verify is a paid API for AI agents from tools.moneytools.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-19).

Verifies an HMAC signature against a message and secret using SHA-256/SHA-1/SHA-384/SHA-512, returning whether the signature is valid

## Facts

- Endpoint: POST https://tools.moneytools.dev/v1/hmac-verify?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/moneytools-hmac-verify-1eccd0e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gi_2gF-6mTXIAOWCfruxi

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 moneytools-hmac-verify-1eccd0e6 -d '<json body>'
```

Example prompt: Can you verify this webhook HMAC signature for me? The secret is 'whsec_mykey', the raw message body is '{"id":42,"event":"payment.completed"}', the expected signature is 'a3f2c...' in hex, and we're using SHA-256.

## When to prefer this

Use this endpoint when you need a lightweight, stateless HMAC signature check without setting up your own crypto library — ideal for verifying webhook payloads from services like Stripe, GitHub, or Shopify, or for authenticating internal signed messages. Prefer it when you want a cheap (sub-cent), read-only, audit-free verification call that supports multiple hash algorithms and both hex and base64 encodings.

## Known failure modes

- Invalid or unsupported algorithm value (not sha256/sha1/sha384/sha512)
- Malformed signature encoding (neither valid hex nor base64)
- Missing required fields (secret, message, or signature) causing a 400 error
- Signature mismatch returns a valid response but with invalid=true rather than an error
- Network or service unavailability returning a 5xx error
- Payment failure (402) if no credits or x402 payment provided

## How this service works

Catalog of MoneyTools: 116 cheap, read-only tools for AI agents. Free daily tier, then x402 USDC micropayments or prepaid credits. Token safety, approvals, tx decoding, EIP-712 risk, gas, ENS, x402 validation, DNS, RDAP, JSON Schema, time, FX.

## Output

A JSON response indicating whether the provided signature is valid for the given message and secret, using the specified HMAC algorithm and encoding. Likely includes a boolean valid/invalid result and possibly the computed HMAC for comparison.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "algo": {
   "type": "string",
   "examples": [
    "sha256"
   ],
   "description": "sha256 | sha1 | sha384 | sha512"
  },
  "secret": {
   "type": "string",
   "examples": [
    "whsec_test"
   ],
   "description": "HMAC secret (not stored)"
  },
  "message": {
   "type": "string",
   "examples": [
    "{\"id\":1}"
   ],
   "description": "raw message / body"
  },
  "signature": {
   "type": "string",
   "examples": [
    "00"
   ],
   "description": "expected signature (hex or base64)"
  },
  "signatureEncoding": {
   "type": "string",
   "description": "hex | base64 (auto)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "algo": "SHA-256",
  "note": "Secret is taken from this request body only and is never stored or logged. Use for webhook authenticity checks.",
  "valid": false,
  "signatureHex": "28b662b0d2478f16dfe24997114352f1e753db9b7b114b477859947e73144763",
  "expectedLength": 32,
  "providedLength": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/moneytools-hmac-verify-1eccd0e6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tools.moneytools.dev](https://www.zero.xyz/host/tools.moneytools.dev/llms.txt)
