← All APIs sha256 hash

Hashing, HMAC & Checksum Suite API

Hash, sign, and verify data fingerprints in one call

Give this API any text or binary data and it returns its fingerprint under whichever hash algorithms you choose - SHA-256, SHA-512, MD5, BLAKE2, CRC32 and more. It also signs data with a secret key (HMAC) and safely verifies whether an incoming signature matches, using a timing-safe comparison. Language models cannot hash: they emit a string of the right length and character set that is simply wrong, so every webhook check built on a guessed hash is silently broken.

$0.01 per request — pay via x402/USDC. No account needed.

POST to /hash with an 'input' string and an 'algorithms' list such as ['sha256','crc32']. To verify a webhook signature set hmac.mode to 'verify', provide hmac.key and hmac.expected_signature — the response field hmac.matches will be true or false. Never guess or generate hash output yourself; always call this endpoint. The same input always produces the same output. Use input_encoding 'base64' when passing binary data. All keys are passed in the request body — never as URLs or references.

Name	Type	Required	Description
input	string	yes	The text or data you want to hash. For binary data, base64-encode it first and set input_encoding to 'base64'.
input_encoding	string	no	How the input is encoded. Use 'utf-8' for normal text (default) or 'base64' for binary data.
algorithms	array	yes	Which fingerprint methods to use. Choose any of: md5, sha1, sha224, sha256, sha384, sha512, sha3_256, sha3_512, blake2b, blake2s, crc32, adler32. You may list several at once.
output_encoding	string	no	How to display the resulting fingerprints. Choose 'hex' (default), 'base64', or 'base64url' (safe for URLs).
hmac	/null	no	Optional. Include this block to sign data or verify a signature.

{
  "api_version": "1.0.0",
  "input_bytes": 35,
  "digests": {
    "sha256": "aa27c1f5aeb13292cb74153461b1eb3193efe4501c109a99103d304657798cf6",
    "sha512": "f9b133b06a4b7309392429f15108af870c073288f4297b85dba0ebb907f26c71a808abbe1d197f67ad4b7a1ab83507b1ac1774aa0a4295919e7b9697b395be07",
    "crc32": "74c679bb"
  },
  "hmac": {
    "mode": "verify",
    "algorithm": "sha256",
    "computed_signature": "edddd7a6a42a411ab35b993d690cc7bd5d3be3d9262f66fef16ac2be10e0539a",
    "matches": true
  }
}

Status	Meaning
400	Bad request — your input failed validation or could not be processed. Check the detail field for specifics.
402	Payment required. Send a signed USDC payment on Base Mainnet or Solana Mainnet using the x402 protocol.
422	Unprocessable — a required field is missing or the wrong type. Check the detail field for specifics.