← All news

News

New: Hash Lookup Endpoint

Jul 07, 2026 additionupdatechangelog

You can now check whether a piece of content has already been scored without re-sending the text or re-uploading the image.

Every moderation response already returns a hash. Pass it back to the new endpoint to instantly see if (and how) that content was scored, without spending a model call:

GET /v1/moderate/{category}/hash/{hash}

category is one of text, image, or scam (uses the matching key toggle) hash is the 64-char SHA-256 digest from any prior response

Example curl https://api.modapi.xyz/v1/moderate/text/hash/9f86d081...2f4b2d \ -H "Authorization: Bearer $API_KEY"

{ "category": "text", "hash": "9f86d081...2f4b2d", "present": true, "confidence": { "scam": 0.90, "toxic": 0.00, "harassment": 0.00, "hate": 0.00 }, "route": "/v1/moderate/text/hash" }

If the hash isn't cached yet, present is false and confidence is null. A miss is not an error, it just means nothing's been scored under that hash.

Also: the search endpoint is seperate to the scan endpoints and comes with a huge benefit. Search endpoints have 5x the scan endpoint of each plan, look in the docs for detailed info!

📚 Docs also refreshed

The docs (https://api.modapi.xyz/docs) now cover everything shipped recently: The new Hash Lookup endpoint The hash field returned on every moderation response Rules & annotations: reshape your own results (flag / unflag / annotate) from Dashboard → Rules