Skill

Screen People and Organisations for Adverse Media & Sanctions

Screens a person or organisation for adverse media, PEP status, and sanctions exposure, always returning review, never a guilty verdict.

Works with stipple

91
Spark score
out of 100
Updated 17 days ago
Source checked Sep 3, 2026
Version 16.6.0

Add to Favorites

Why it matters

Conduct AML/CTF-compliant adverse media, PEP, and sanctions screening for individuals and organisations during onboarding, vendor due diligence, or ongoing counterparty monitoring, returning corroboration-gated results that flag review needs without declaring guilt.

Outcomes

What it gets done

01

Search adverse media coverage across corroborated sources for a named person or organisation

02

Check for Politically Exposed Person (PEP) status and sanctions list exposure

03

Extract and summarise adverse media hits with dates, sources, and URLs for human review

04

Generate screening reports with compliant framing that distinguishes review flags from determinations

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-screen-adverse-media | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

Screen Adverse Media

This skill screens a person or organisation for adverse media coverage, PEP status, and sanctions exposure via the Stipple API, corroborating every hit across sources and always framing results as review, never as a verdict. Use it for AML/CTF onboarding, vendor or supplier due diligence, investor vetting, or ongoing counterparty monitoring.

What it does

This skill screens a person or organisation for adverse media coverage, PEP (Politically Exposed Person) status, and sanctions exposure, using the Stipple API. Every hit is corroboration-gated across sources before inclusion: the result is always framed as "review," never "guilty," and "nothing found" is never presented as a clean record.

When to use - and when NOT to

Use it for AML/CTF onboarding, where Tranche 2 reforms make this mandatory for more Australian businesses, vendor or supplier due diligence before signing, investor or LP vetting, or ongoing counterparty monitoring where the screen is re-run periodically and warrant IDs are compared over time. This is not a legal AML/CTF determination on its own - a qualified human reviewer must resolve identity ambiguity, document the reasoning, and provide an appropriate correction or appeal path before rejecting or restricting a person or organization, and no allegation should be published as fact.

Inputs and outputs

Input is a person's or organization's name, screened via an MCP tool call, or a document such as an ID or company extract submitted over REST:

curl -X POST https://www.stipple.sh/v1/adverse-media \
  -F "file=@company-extract.pdf" \
  -H "Authorization: Bearer $STIPPLE_API_KEY"

Output is an overall rating such as review or clear, a hits list of adverse media articles with date, title, source, URL, and summary, a pep list that is empty when nothing is found, and a sanctions list that is likewise empty when clear. Framing is fixed rather than left to interpretation: hits found reads as "review recommended - see articles below," never "guilty"; nothing found reads as "no corroborated adverse media found - this is NOT a clean record, coverage is bounded by the source list"; a PEP signal reads as "enhanced due diligence may apply." A real report might list a 2025 court action over unpaid supplier debts alongside an earlier regulator disqualification, each with its own source and link, next to zero PEP and zero sanctions signals - and the report still leads with the reminder that this is the start of human review, not the end of it.

Integrations

The Stipple API performs the screen at 3 credits per run against a free weekly allowance, with a free key available for metering beyond that. For a full AML workflow, it pairs with the check-identity-pack skill for identity and verify-document for document genuineness.

Who it's for

Compliance, onboarding, and investment teams running AML/CTF or supplier due-diligence screens who need corroborated results with explicit "review, not guilty" framing rather than a binary pass or fail.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.