ComputeFirst

Compute a SHA-256 hash from an AI agent

You need a digest of a piece of text or of encoded bytes, for example to compare it with a published checksum.

**Use hash-digest-compute@1.0.0.** It is free and needs no key or sign-up. Compute a message digest (SHA-2, SHA-3, BLAKE2/3, MD5, RIPEMD-160, Keccak-256) over encoded input bytes.

Why call a tool for this

A model cannot reliably work out a hash by reasoning, and a made-up digest looks just like a real one. The tool computes it and returns hex, base64 and base64url together.

Call it over HTTP

curl -X POST https://computefirst.net/v1/tools/hash-digest-compute/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"text":"abc","algorithm":"sha256"}'

Response:

{
  "result": {
    "algorithm": "sha256",
    "input_bytes": 3,
    "output_bytes": 32,
    "hex": "ba7816bf8f01cfea414140de5dae2223b00361a396177a9cb410ff61f20015ad",
    "base64": "ungWv48Bz+pBQUDeXa4iI7ADYaOWF3qctBD/YfIAFa0=",
    "base64url": "ungWv48Bz-pBQUDeXa4iI7ADYaOWF3qctBD_YfIAFa0",
    "collision_broken": false
  }
}

Call it over MCP

Connect https://computefirst.net/mcp (setup), then call execute with:

{
  "id": "hash-digest-compute",
  "version": "1.0.0",
  "input": {
    "text": "abc",
    "algorithm": "sha256"
  }
}

Check the result

Hash the exact bytes you mean to hash: a trailing newline changes the digest. The response flags algorithms with known collisions in collision_broken.

Full contract, limits and unsupported cases: Hash digest compute.