Tamper-detection verification for TunnelMind surveillance receipts. Submit the
receipt ID, the SHA-256 content hash, and the Ed25519 signature from the receipt
document. The registry compares these against what was recorded at issuance time.
Returns VALID if both match exactly, INVALID with a specific mismatch reason otherwise.
Use this tool when:
- You received a surveillance receipt document and want to verify it hasn't been altered.
- You are programmatically checking receipt authenticity in an agent workflow.
- You want to prove to a third party that a receipt is genuine.
Do NOT use this tool when:
- You only want to check existence — use `get_receipt` instead (no body required).
- You want jurisdiction certificate verification — use `verify_ghostroute_cert` instead.
Inputs:
- `receipt_id` (body, required): The receipt's ID field from the document.
- `content_hash` (body, required): SHA-256 hex hash of the receipt JSON. Max 256 chars.
- `signature` (body, required): Ed25519 signature from the receipt document. Max 512 chars.
Returns:
- `valid`: boolean. True only if both hash and signature match exactly.
- `status`: `VALID` or `INVALID`.
- `message`: human-readable explanation. On INVALID, specifies whether the hash
mismatched, the signature mismatched, or both.
Cost:
- Free. No API key required.
Latency:
- Typical: <100ms, p99: <300ms.
Connector