Skip to main content
Slack has a live verifier today. Once your workspace is connected, QED Proof can decide a slack.message.post claim by reading Slack itself — never by trusting what your agent reported.

Access

  • Reads channels you can see
  • No direct messages
  • Never posts, edits or deletes

Scopes

What it verifies

verifier
Checks that a message with exactly the claimed timestamp exists in the claimed channel and, optionally, that its text matches a fingerprint your agent supplies. The claim’s team_id is bound to your workspace’s connection; a team with no connection gives unverifiable / no_connection. A ts present but with a different text fingerprint is mismatch / content_mismatch. No message with that ts by the deadline is failed / not_found. Direct messages are out of scope.Target: slack://<team_id>/<channel_id>. Params: ts — the message timestamp Slack returned when it was posted. text_sha256 (optional) — lowercase hex SHA-256 of the normalized message text.
See the profile for the exact match rules, windows and required access.