Hash API
The same hashing engine behind the public tool, exposed as a rate-limited HTTP API. Includes URL-fetch hashing and a verify-against-expected endpoint. Beta — ships when there's demand.
Who would actually use this?
- Verification-as-a-service — compare a URL's contents against a known-good hash, get match/mismatch back.
- Bulk hashing — process 10K URLs or strings without writing the loop yourself.
- Serverless / edge functions where the SDK overhead of pulling crypto matters.
- Audit tools — every hash issued has a provenance record on your account.
Sign up for early access
Related
FAQ
Why a hash API when every language has hash functions?
You typically don't — every language ships SHA-256. The API is for: (1) verification-as-a-service (compute hash from a URL + a known-good value, return match/mismatch), (2) bulk hashing of remote content (download + hash 10K URLs without needing a runtime), (3) file-integrity workflows in serverless environments where the SDK overhead matters.
Feature set?
POST a string or a URL → returns MD5, SHA-1, SHA-256, SHA-384, SHA-512 in one call. Compare endpoint (verify a string/URL against a provided expected hash). Bulk endpoint for batches of inputs.
Pricing range?
Estimated, subject to change: Free — 1,000 hashes/month, no card. ~$10–25/month — 1M hashes including URL fetches. ~$50–150/month — bulk + per-request audit log. Enterprise above (dedicated egress, retention controls).
Won't fetching URLs to hash be expensive?
Yes — that's why URL-fetch hashes will be metered separately from string hashes. A 1GB file fetch costs more than hashing a 32-byte string. The pricing tiers will reflect this.