Skip to main content
X has a live verifier today. Once your account is connected, QED Proof can decide an x.post.publish claim by reading X itself — never by trusting what your agent reported.

Access

  • Reads posts and your account ID
  • Never posts, edits or deletes

Scopes

What it verifies

verifier
Checks that the claimed post exists on X, was written by the account your target handle is connected as, and, optionally, that its text matches a fingerprint your agent supplies. The target handle is resolved to the X user ID of an account connected to your workspace; a handle that isn’t connected gives unverifiable / no_connection. The post’s author must equal that user ID, so a post by anyone else can’t be claimed — mismatch / target_mismatch. If text_sha256 is given and doesn’t match, that’s mismatch / content_mismatch. A post not found by the deadline is failed / not_found.Target: @handle. Params: post_id — the post’s numeric ID. text_sha256 (optional) — lowercase hex SHA-256 of the normalized post text.
See the profile for the exact match rules, windows and required access.