This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
say-do-diff
Catch AI agent replies that claim more than the tools did
Free MIT licensed Python checker for AI agents. It finds claims like sent or refunded in the final reply and grades each against the run tool log. Flags queued emails, failed refunds, partial batches and duplicates. CLI, GitHub Action, n8n, LangChain.
Hi Product Hunt. say-do-diff is a small checker for one agent failure: the final reply says "I sent it" or "refunded" or "all set," but the tool calls in that run do not back it up. Common causes are an email API that returned 202 (queued), a payment call that timed out, or 3 of 5 sends landing when the reply says all 5.
You give it the reply and the run tool log. It pulls out each completed action claim, matches it to calls by action and target, grades the evidence from S0 (no call) to S4 (verified afterwards), and flags claims whose wording needs more than the evidence shows. It also catches wrong targets, amount mismatches and duplicate sends. Python stdlib only, no model in the loop, MIT licensed. Exit codes work in CI. It also runs as a GitHub Action and can read logs from n8n, LangChain, planlock, and Microsoft Agent Governance Toolkit.
Important limits: English only with a fixed verb list, so a clean report is not proof the reply is honest. It trusts the log as written. It only reports and does not change the reply. The CLI checks the reply against tool logs. It does not open files or show an automatic file content diff.
If you need the check inline before the reply goes out, with HMAC signed receipts written by your tool layer using a key the model never sees, that is the Say-Do Gate ($49): https://solokit33.gumroad.com/l/...
We would value feedback on two things: which APIs give you "accepted" responses that agents report as done, and whether requiring an object id for "done" is too strict.
About say-do-diff on Product Hunt
“Catch AI agent replies that claim more than the tools did”
say-do-diff was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #744 on the daily leaderboard. Free MIT licensed Python checker for AI agents. It finds claims like sent or refunded in the final reply and grades each against the run tool log. Flags queued emails, failed refunds, partial batches and duplicates. CLI, GitHub Action, n8n, LangChain.
On the analytics side, say-do-diff competes within Open Source, Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1.1M followers on Product Hunt. The dashboard above tracks how say-do-diff performed against the three products that launched closest to it on the same day.
Who hunted say-do-diff?
say-do-diff was hunted by SoloKit Studio. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of say-do-diff including community comment highlights and product details, visit the product overview.
Hi Product Hunt. say-do-diff is a small checker for one agent failure: the final reply says "I sent it" or "refunded" or "all set," but the tool calls in that run do not back it up. Common causes are an email API that returned 202 (queued), a payment call that timed out, or 3 of 5 sends landing when the reply says all 5.
You give it the reply and the run tool log. It pulls out each completed action claim, matches it to calls by action and target, grades the evidence from S0 (no call) to S4 (verified afterwards), and flags claims whose wording needs more than the evidence shows. It also catches wrong targets, amount mismatches and duplicate sends. Python stdlib only, no model in the loop, MIT licensed. Exit codes work in CI. It also runs as a GitHub Action and can read logs from n8n, LangChain, planlock, and Microsoft Agent Governance Toolkit.
Important limits: English only with a fixed verb list, so a clean report is not proof the reply is honest. It trusts the log as written. It only reports and does not change the reply. The CLI checks the reply against tool logs. It does not open files or show an automatic file content diff.
If you need the check inline before the reply goes out, with HMAC signed receipts written by your tool layer using a key the model never sees, that is the Say-Do Gate ($49): https://solokit33.gumroad.com/l/...
Free 10 minute manual checklist: https://solokit33.gumroad.com/l/...
We would value feedback on two things: which APIs give you "accepted" responses that agents report as done, and whether requiring an object id for "done" is too strict.