#️⃣Hash Calculator
Compute exact hash digests of UTF-8 text using Web Crypto (SHA family) and a verified pure-JS MD5 for legacy checksums. Deterministic — identical input always yields the identical digest.
Worked examples
SHA-256 of "hello"
GET /api/v1/dev/hash?text=hello&algo=sha256
Result: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
SHA-512 of a seed phrase
GET /api/v1/dev/hash?text=test%20seed%20phrase&algo=sha512
Result: 793daabf23d746ed72a1d1fb750cf202c7f32c0481649435b670cd949ab0f7b8298bb97fc28bcae6bbebedbed72be26dd282763b402ce0282e03d2b0046592e3
MD5 of the classic pangram
GET /api/v1/dev/hash?text=The%20quick%20brown%20fox%20jumps%20over%20the%20lazy%20dog&algo=md5
Result: 9e107d9d372bb6826bd81d3542a419d6
Machine API (x402)
$0.001 / callThis tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.
GET /api/v1/dev/hash?text=hello&algo=sha256 HTTP/1.1
Host: agenttools-hub.vercel.app
→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)
{
"tool": "dev/hash",
"input": {"text":"hello","algo":"sha256"},
"result": { "value": null, "answer": "2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824" }
}Agent docs: /llms.txt · OpenAPI spec · integration guide
About this tool
Exact hash digests computed with the platform's Web Crypto implementation: SHA-256 and SHA-512 for modern integrity checks, SHA-1 and MD5 for legacy checksum compatibility. Hashing is deterministic — the same bytes always produce the same digest, which is exactly what LLMs must not approximate.
Frequently asked questions
Is MD5 safe?
No for security (collisions are practical), yes for non-adversarial checksums like dedup keys. Prefer SHA-256 everywhere new.
Is the input hashed as UTF-8?
Yes — text is encoded as UTF-8 first. Hashing binary files requires hashing their bytes, not a text rendering.