BCrypt Verify
Verifies whether a password matches a stored BCrypt hash. The work factor is read from the hash itself, so verification costs the same as the hashing did.
receipt_long
Why 2 credits?
Verification runs the same deliberately slow key derivation as hashing, at whatever work factor is embedded in the supplied hash.
Any HTTP client works. Replace the key with one from your dashboard.
bash
curl -X POST https://toolkitbackend-j69m.onrender.com/api/v1/tools/bcrypt-verify \
-H "Authorization: Bearer tb_live_<your_api_key>" \
-H "Content-Type: application/json" \
-d '{
"password": "correct horse battery staple",
"hash": "$2a$11$..."
}'Input
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
password | string | required | - | Plaintext password to test. |
hash | string | required | - | The stored BCrypt hash to test against. |
Output
| Field | Type | Description |
|---|---|---|
matches | boolean | True when the password produces the supplied hash. |
Try it
Sends a real POST /api/v1/tools/bcrypt-verify from your browser and charges 2 credits to your account.
Sign in to run this endpoint. New accounts start with free credits.