Skip to main content
Adverse media categories describe the type of risk Minerva found in an article. Administrators can choose which categories Minerva is allowed to emit for each screening channel, while API integrations can override that choice for one synchronous search or one entity in a batch. Access: Requires the Admin role or above. In the sidebar, go to Administration > Configuration > Adverse Media, then open Adverse Media Risk Classification. Use this guide when you need to:
  • align adverse media output with your AML, KYC, background-check, or general screening policy
  • add or remove categories independently across Minerva’s four screening channels
  • understand the distinction between financial and non-financial crime risk categories
  • preserve a known API response contract while testing newly introduced categories
  • override the category set for one synchronous search or one entity in a batch
Category configuration is workspace-scoped. A Calibration workspace can use a different category set from Live, and changing one workspace does not change another.
A risk category is a machine-learning classification of article content, not a finding of guilt, a legal conclusion, or proof that the article concerns the screened subject. Review the identity evidence, source, article context, jurisdiction, dates, and case disposition before making a decision.

How Category Classification Works

Minerva evaluates qualifying adverse media articles for sentiment and one or more supported risk topics. An article can receive more than one risk category when its content supports multiple themes. For example, reporting about a bribery scheme that launders proceeds through real estate can support Fraud/Bribery/Corruption, Money Laundering, and Real Estate. The category configuration is an allow-list:
  • an enabled category may appear when the model finds enough evidence for it
  • a disabled category cannot appear in adverse media risk scores or article flags and cannot contribute to screening outcomes
  • enabling a category does not force Minerva to assign it
  • disabling a category does not stop article retrieval or disable the News feed
  • category changes affect subsequent searches and article processing; they do not rewrite completed search results
The model’s internal no-risk outcome is not a configurable category.

Financial And Non-Financial Risk

The two groups help administrators align the category set with the purpose of a screening program. They are configuration groupings, not legal classifications.

Financial Crime Risks

The Financial Crime Risks group contains 28 AML-relevant themes. Its scope is intentionally broader than money laundering alone and includes:
  • money laundering, movement of value, concealment of ownership, and sanctions evasion
  • alleged predicate offences that may generate criminal proceeds, such as fraud, bribery, corruption, narcotics trafficking, human trafficking, smuggling, tax evasion, and organized crime
  • terrorist activity and terrorist financing
  • products, services, sectors, and assets that can be abused to move or disguise value, such as cryptocurrency, money service businesses, foreign exchange, real estate, casinos, art, precious materials, auctions, and luxury vehicles
These labels help surface media that may be relevant to customer due diligence, enhanced due diligence, transaction-monitoring context, or suspicious activity review. Whether a theme is in scope for a particular AML program depends on the organization’s jurisdiction, products, customer base, risk assessment, and procedures.
A sector-oriented category does not mean that ordinary activity in that sector is adverse. Minerva assigns risk categories from the article’s adverse context—for example, laundering through an auction house—not merely because the article mentions an auction.

Non-Financial Crime Risks

The Non-Financial Crime Risks group covers adverse conduct that is useful for background checks, safety reviews, or broader criminal-risk screening but is not, by itself, a financial-crime theme:
  • Other (Non-Financial) is the legacy catch-all for serious adverse conduct that does not fit a specific financial category
  • DUI covers impaired-driving offences
  • Property Damage covers vandalism and other attributed damage to property
  • Assault and Battery covers physical violence against another person
An article may still receive both financial and non-financial categories when the facts support both. For example, an alleged assault connected to an organized-crime enterprise can support Assault and Battery and Organized Crime.

Default Category Set

New and previously unconfigured workspaces preserve Minerva’s established 29-category response contract:
  • all 28 financial crime categories are enabled
  • Other (Non-Financial) is enabled
  • DUI, Property Damage, and Assault and Battery are disabled until an administrator enables them
This default prevents newly introduced risk-score keys from appearing unexpectedly in customer integrations. Enable a new category only after downstream mappings, reports, rules, and API consumers are ready to accept it.

Financial Crime Category Reference

Non-Financial Category Reference

Configure Categories Across Screening Channels

The configuration page separates four channels: To change a workspace:
  1. Select the intended workspace, such as Calibration or Live.
  2. Open the channel tab you want to change.
  3. Check a category to allow it, or clear it to prevent it from being emitted.
  4. Use Select all categories only when every downstream consumer can accept all supported keys.
  5. Use Restore defaults to return that channel to the standard 29-category set.
  6. Repeat the review for each channel that needs a different category set.
  7. Select Review changes, confirm the affected channels and categories, add a clear change description, and save.
Use History to review prior deployments or restore an earlier configuration. A rollback creates a new history entry and preserves the audit trail.
Start with one channel in a Calibration workspace. Compare true-positive retention, false-positive volume, reports, rules, and downstream API mappings before reproducing the approved configuration in Live.
The Direct API Calls channel supplies the workspace default for API searches. An integration can replace that default for one call by sending the raw category keys in:
Resolution order is:
  1. request-level global_filters.adverse_media_risk_categories
  2. the selected workspace’s Direct API Calls configuration
  3. the standard 29-category default when no workspace configuration exists
A request override can narrow or widen the workspace set. It can therefore enable a category that the workspace leaves disabled. An empty array disables every adverse media risk category for that call. Unknown keys are rejected with an HTTP 400 response that identifies the invalid values. The override changes category emission only. It does not add the News feed or broaden article retrieval, so include News in feeds when the search should perform adverse media analysis. Place the override in the POST /v1/search-sync request body:
See Search Sync: adverse media risk categories configuration for the live request schema. Place the override inside each applicable object in requests[]. Each entity can use a different category set:
See Batch Search: adverse media risk categories configuration for the live request schema.