AI AGENTS
Teardown Fact-Checker with Disputed-Claim Tickets
When a draft teardown is submitted, the agent independently fact-checks every claim against fresh sources, rewrites or removes the ones that fail.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives draft teardown + competitorHTTP webhook
- ActionExtract claims; verify each against Exa sourcesExa
- ActionRewrite supported/correctable claims into clean draftOpenAI
- LogicBranch: route still-disputed claims to ticketing
- OutputOpen a Linear ticket per disputed claimLinear
What it does
It acts as an adversarial reviewer for a teardown someone already wrote. The agent re-verifies each claim against live sources, fixes what it can, and turns anything still in doubt into a tracked Linear ticket instead of silently shipping a guess.
When to use it
When analysts draft teardowns fast and you need a verification layer before they go to sales or leadership. Use it to catch stale pricing, wrong feature claims, and unsourced assertions with an auditable trail.
How it works
- 1A webhook receives a draft teardown and the competitor it covers.
- 2The agent extracts every factual claim from the draft into a checklist.
- 3For each claim, Exa retrieves current sources and the agent rules it supported, outdated, or contradicted.
- 4Supported and easily corrected claims are rewritten inline into a cleaned draft.
- 5A branch handles the rest: any claim that stays disputed after the search becomes a Linear issue with the claim, the conflicting evidence, and a verify-this label.
- 6The cleaned draft plus links to the open tickets is returned so the author resolves disputes before publishing.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ExaNeural search across the web.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.