> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gu1.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration Provider Codes

> Reference guide for all available integration provider codes — across gu1 marketplace integrations for verification and enrichment.

## Overview

Provider codes are used when configuring automatic integrations during entity creation. This reference lists **enrichment** codes (`*_enrichment`) only.

<Warning>
  **`*_check` provider codes and `POST /integration-execution/marketplace/check` were removed (2026-06-04).** Use the matching **`*_enrichment`** code with [Execute enrichment](/en/api-reference/enrichment/execute-by-id). Legacy create/import payloads that still send `*_check`, `checks`, or `executeAllActiveChecks` are ignored at parse time.
</Warning>

## Normalized Enrichment Field Catalog

Under **Data points provided**, field names refer to consolidated **`normalized_enrichment`** data (`NormalizedPersonEnrichment` / `NormalizedCompanyEnrichment`): root scalars, consolidated arrays (e.g. `sanctions`, `addresses`), and matching `*Summary` fields when applicable.

<Info>
  **Source of truth in code:** `packages/integrations/src/normalization/normalized-field-providers.ts` (`NORMALIZED_FIELD_PROVIDERS`, `getFieldsProvidedBy`). To print every `ValidProviderCodesEnum` value with its mapped fields (or an empty list when not in this catalog), run:

  ```bash theme={null}
  npm run docs:provider-normalized-fields
  ```

  Add `--json` to the script invocation for machine-readable output (`npx tsx scripts/docs/provider-normalized-fields-report.ts --json`).
</Info>

## Provider Code Format

Provider codes follow this naming convention:

```
{country}_{provider}_{check_type}_{integration_type}
```

* **country**: ISO 3166-1 alpha-2 code (e.g., `br`, `ar`, `cl`, `mx`) or `global`
* **provider**: Name of the data provider (e.g., `bdc`, `amldd`, `complyadvantage`)
* **check\_type**: Type of data being retrieved (e.g., `kyc`, `pep`, `sanctions`)
* **integration\_type**: Prefer `enrichment` for new work (`*_enrichment`).

## Integration Types

### Enrichments

Data enrichment that returns detailed information to populate entity profiles. This page documents enrichment codes only.

### Marketplace Service Integrations (`service`)

Catalog integrations with `integration_type = service` expose **organization-scoped** HTTP routes (session or API key with tenant). The organization must **enable** the integration in Marketplace like any other product.

* **Base path:** `/api/integration-services/:integrationCode/...` (same auth and `organizationId` context as the rest of the API).
* **Full reference:** see the [Marketplace Services](/en/api-reference/services/overview) section — overview, per-service guides, and one page per endpoint (request/response, errors, billing).
* **Example code:** `ar_gueno_holder_intelligence_service` — [CBU/CVU Holder Intelligence](/en/api-reference/services/ar-gueno-holder-intelligence/overview) (Argentina CUIT-linked totals and custom metrics).

Per-request billing follows the same **execution pack or credits** rules as other paid marketplace integrations when `base_price_cents` is greater than zero (the catalog row is seeded **free** by default).

### Marketplace List Integrations (`lists`)

Catalog integrations with `integration_type = lists` allow an **existence-only** check: whether a given string appears in that list’s marketplace items (`primary_value` / `search_keys`). There is **no** tenant HTTP API to download or page the full list contents.

* **Base path:** `/api/marketplace-list-lookups/:integrationCode/lookup` (same auth and `organizationId` context as the rest of the API). Requires permission to read marketplace (`marketplace:read` / legacy equivalent).
* **Request:** `POST` with JSON body `{ "value": "<string>" }` (`value` length capped server-side).
* **Success response:** `{ "success": true, "data": { "found": true | false } }` — no item payloads, match arrays, or catalog dumps.
* **Not enabled for org:** HTTP `404` with error code `LIST_INTEGRATION_NOT_ACTIVE` (same idea as inactive service integrations).

Lookups use the same marketplace billing path as other list lookups when the product is priced.

## Available Provider Codes

### Brazil (BR)

#### BDC (Big Data Corp)

**Enrichments:**

* `br_bdc_basic_data_enrichment` - Basic person/company data

<Expandable title="Data points provided">
  `age`, `dateOfBirth`, `fatherName`, `fullName`, `gender`, `isDeceased`, `motherName`, `nationality`, `situation`, `socialSecurityNumber`, `taxId`
</Expandable>

* `br_bdc_related_persons_enrichment` - Related persons data

<Expandable title="Data points provided">
  `fatherName`, `motherName`, `relationships`
</Expandable>

* `br_bdc_judicial_processes_enrichment` - Complete judicial records

<Expandable title="Data points provided">
  `criminalRecords`, `legalProceedings`
</Expandable>

* `br_bdc_financial_data_enrichment` - Financial profile data

<Expandable title="Data points provided">
  `incomeRange`, `taxReturns`, `totalAssetsCategory`
</Expandable>

* `br_bdc_addresses_extended_enrichment` - Complete address history

<Expandable title="Data points provided">
  `address`, `addresses`, `city`, `country`, `postalCode`, `state`
</Expandable>

* `br_bdc_emails_extended_enrichment` - Email verification and history

<Expandable title="Data points provided">
  `email`, `emails`
</Expandable>

* `br_bdc_phones_extended_enrichment` - Phone verification and history

<Expandable title="Data points provided">
  `phone`, `phones`
</Expandable>

* `br_bdc_related_companies_enrichment` - Related companies data

<Expandable title="Data points provided">
  `employer`, `occupation`, `relationships`, `shareholders`
</Expandable>

* `br_bdc_lawsuits_enrichment` - Detailed lawsuit information

<Expandable title="Data points provided">
  `criminalRecords`, `legalProceedings`
</Expandable>

* `br_bdc_kyc_person_enrichment` - Complete person KYC data

<Expandable title="Data points provided">
  `isCurrentPep`, `isPep`, `last180DaysSanctions`, `pepLevels`, `sanctioned`, `sanctions`, `sanctionsSummary`
</Expandable>

* `br_bdc_kyc_business_enrichment` - Complete business KYC data

<Expandable title="Data points provided">
  `isCurrentPep`, `isCurrentlyElectoralDonor`, `isHistoricalElectoralDonor`, `isPep`, `last30DaysSanctions`, `last365DaysSanctions`, `last3YearsPEPOccurence`, `last5YearsPEPOccurence`, `last90DaysSanctions`, `lastYearPEPOccurence`, `pepLevels`, `registrationCountry`, `sanctioned`, `sanctions`, `sanctionsSummary`, `totalElectoralDonationAmount`, `totalElectoralDonations`, `wasPreviouslySanctioned`
</Expandable>

* `br_bdc_negative_media_enrichment` - Negative media articles

<Expandable title="Data points provided">
  `adverseMediaScore`, `hasAdverseMedia`, `mediaMentions`
</Expandable>

* `br_bdc_negative_media_company_enrichment` - Negative media exposure for companies (CNPJ)

<Expandable title="Data points provided">
  `adverseMediaScore`, `hasAdverseMedia`, `mediaMentions`
</Expandable>

* `br_bdc_revenue_estimate_enrichment` - Revenue estimates and trends

<Expandable title="Data points provided">
  `employeeCount`, `incomeRange`
</Expandable>

* `br_bdc_shareholders_enrichment` - Complete shareholder structure

<Expandable title="Data points provided">
  `shareholders`
</Expandable>

* `br_bdc_reputation_reviews_enrichment` - Reputation scores and reviews

<Note>
  These keys are the main **company** fields produced by this enrichment (see `providersExpectedFields` in code). They may not all appear in `getFieldsProvidedBy` until mapped in `normalized-field-providers`.
</Note>

<Expandable title="Data points provided">
  `averageRating`, `complaintResolutionRate`, `complaintResponseRate`, `firstReviewDate`, `hasSignificantNegativeReviews`, `lastReviewDate`, `maxReputationRating`, `minReputationRating`, `negativeReviewsPercentage`, `positiveReviewsPercentage`, `recentReputationScore`, `recentReviewsCount`, `reputationScore`, `reviewSourcesCount`, `totalReviews`
</Expandable>

* `br_bdc_protestos_enrichment` - Detailed protestos records

<Note>
  Main **person/company** summary fields from protest data (expected shapes in code). Consolidated top-level mapping in `normalized-field-providers` may be partial.
</Note>

<Expandable title="Data points provided">
  `hasProtestos`, `newestProtestDate`, `oldestProtestDate`, `protestsByState`, `protestosCount`, `protestosTotalValue`
</Expandable>

* `br_bdc_faturamento_presumido_enrichment` - Presumed revenue analysis

<Note>
  **Company** revenue / activity indicators (expected fields in code). Same caveat as other BDC enrichments for `getFieldsProvidedBy`.
</Note>

<Expandable title="Data points provided">
  `activityLevel`, `digitalPresence`, `hasActivity`, `hasRecentData`, `revenueRange`, `shellCompanyRisk`
</Expandable>

* `br_bdc_judicial_processes_shareholders_enrichment` - Judicial processes for shareholders

<Expandable title="Data points provided">
  `criminalRecords`, `legalProceedings`, `shareholders`
</Expandable>

* `br_bdc_basic_data_company_enrichment` - Basic company data

<Expandable title="Data points provided">
  `cnaes`, `cnaesSummary`, `companyAge`, `incorporationDate`, `isMEI`, `isSimples`, `legalForm`, `legalName`, `registrationCountry`, `registrationNumber`, `registrationUptimeMonths`, `revenue`, `situation`, `situationDate`, `taxId`, `tipo`, `tradeName`
</Expandable>

#### JusBrasil

**Enrichments:**

* `br_jusbrasil_criminal_lawsuits_enrichment` - Criminal lawsuit details

<Expandable title="Data points provided">
  `criminalRecords`, `fullName`, `legalName`, `legalProceedings`, `registrationNumber`, `taxId`
</Expandable>

* `br_jusbrasil_civil_lawsuits_enrichment` - Civil lawsuit details

<Expandable title="Data points provided">
  `fullName`, `legalName`, `legalProceedings`, `registrationNumber`, `taxId`
</Expandable>

* `br_jusbrasil_labor_lawsuits_enrichment` - Labor lawsuit details

<Expandable title="Data points provided">
  `fullName`, `legalName`, `legalProceedings`, `registrationNumber`, `taxId`
</Expandable>

* `br_jusbrasil_public_ministry_enrichment` - Public ministry records

<Expandable title="Data points provided">
  `fullName`, `legalName`, `legalProceedings`, `registrationNumber`, `taxId`
</Expandable>

* `br_jusbrasil_arrest_warrants_enrichment` - Arrest warrant details

<Expandable title="Data points provided">
  `criminalRecords`, `fullName`, `legalProceedings`, `sanctioned`, `taxId`
</Expandable>

* `br_jusbrasil_irregular_employer_enrichment` - Irregular employer records

<Expandable title="Data points provided">
  `legalName`, `registrationNumber`, `sanctioned`, `taxId`
</Expandable>

#### AMLDD (Anti-Money Laundering Due Diligence)

**Enrichments:**

* `br_amldd_esg_enrichment` - ESG compliance data

<Expandable title="Data points provided">
  `aliases`, `country`, `documents`, `esgNegativeNewsCount`, `esgPositiveNewsCount`, `esgScore`, `fullName`, `hasAdverseMedia`, `legalName`, `mediaMentions`, `registrationCountry`, `registrationNumber`, `taxId`, `tradeName`, `violations`
</Expandable>

* `br_amldd_lri_enrichment` - LRI detailed records

<Expandable title="Data points provided">
  `criminalRecords`, `dateOfBirth`, `documents`, `fullName`, `legalName`, `nationality`, `sanctioned`
</Expandable>

* `br_amldd_pep_enrichment` - PEP complete profiles

<Expandable title="Data points provided">
  `aliases`, `city`, `country`, `dateOfBirth`, `deathYear`, `documents`, `fullName`, `isCurrentPep`, `isPep`, `occupation`, `pepCountry`, `pepLevels`, `pepPosition`, `state`, `taxId`
</Expandable>

* `br_amldd_mtlsn_complete_enrichment` - Complete MTLSN data

<Expandable title="Data points provided">
  `adverseMediaScore`, `aliases`, `criminalRecords`, `documents`, `fullName`, `isPep`, `legalName`, `mediaMentions`, `pepCountry`, `registrationNumber`, `sanctions`, `taxId`, `violations`
</Expandable>

* `br_amldd_mtlsn_simple_enrichment` - Simple MTLSN data
* `br_amldd_mtlsn_with_internal_enrichment` - MTLSN with internal data

#### CPF/CNPJ

**Enrichments:**

* `br_cpfcnpj_complete_person_enrichment` - Complete CPF data

<Expandable title="Data points provided">
  `age`, `country`, `dateOfBirth`, `documents`, `fullName`, `isDeceased`, `situation`, `taxId`
</Expandable>

* `br_cpfcnpj_complete_person_9_enrichment` - CPF data variant (9-digit / alternate flow)

<Expandable title="Data points provided">
  `gender`, `motherName`
</Expandable>

* `br_cpfcnpj_complete_company_enrichment` - Complete CNPJ data

<Expandable title="Data points provided">
  `address`, `addresses`, `city`, `cnaes`, `documents`, `email`, `emails`, `incorporationDate`, `inicioAtividade`, `isMEI`, `isSimples`, `legalForm`, `legalName`, `phones`, `postalCode`, `registrationCountry`, `registrationNumber`, `registrationUptimeMonths`, `revenue`, `shareholders`, `situation`, `situationDate`, `size`, `status`, `taxId`, `tipo`
</Expandable>

#### BrasilAPI

**Enrichments:**

* `br_brasilapi_company_enrichment` - Company data from BrasilAPI
* `br_cnpjws_company_enrichment` - Company registry data from CNPJ.ws (free)
* `br_opencnpj_company_enrichment` - Company registry data from OpenCNPJ (free)

<Expandable title="Data points provided">
  `address`, `addresses`, `city`, `cnaes`, `country`, `documents`, `email`, `emails`, `incorporationDate`, `inicioAtividade`, `isMEI`, `isSimples`, `legalForm`, `legalName`, `phones`, `postalCode`, `registrationCountry`, `registrationNumber`, `registrationUptimeMonths`, `revenue`, `shareholders`, `situation`, `situationDate`, `size`, `state`, `taxId`, `tradeName`
</Expandable>

### Argentina (AR)

#### BCRA (Banco Central de la República Argentina)

**Enrichments:**

* `ar_bcra_deudas_enrichment` - Complete debt records

<Expandable title="Data points provided">
  `debtorStatus`, `fullName`, `legalName`, `taxId`, `totalDebt`, `worstCreditSituation`
</Expandable>

* `ar_bcra_historicas_enrichment` - Historical financial records

<Expandable title="Data points provided">
  `averageMonthlyDebt`, `fullName`, `hasActiveLegalProcesses`, `hasActiveRevisions`, `legalName`, `periodsAnalyzed`, `taxId`, `totalCurrentDebt`, `totalFinancialEntities`, `totalHistoricalDebt`, `worstHistoricalSituation`
</Expandable>

* `ar_bcra_cheques_rechazados_enrichment` - Rejected checks details

<Expandable title="Data points provided">
  `fullName`, `legalName`, `taxId`
</Expandable>

#### Nosis

**Enrichments:**

* `ar_nosis_extended_verification_enrichment` - Extended verification data

<Expandable title="Data points provided">
  `address`, `addresses`, `addressesSummary`, `afipRegistrationDate`, `afipSeniority`, `age`, `companyAge`, `country`, `dateOfBirth`, `employeeCount`, `employmentSeniority`, `firstName`, `fullName`, `gender`, `idNumber`, `idType`, `incorporationDate`, `isAMLObligatedSubject`, `isAutonomous`, `isCurrentPep`, `isDeceased`, `isEmployee`, `isEmployer`, `isIncomeTaxRegistered`, `isIvaRegistered`, `isMemberOfCompany`, `isMonotributo`, `isPep`, `isRetired`, `laftHomonymsCount`, `lastName`, `legalForm`, `legalName`, `occupations`, `occupationsSummary`, `pepLevels`, `riskFlags`, `riskFlagsSummary`, `taxId`, `wasEmployedLast12Months`
</Expandable>

#### REPET (Registro Público de Empleadores con Sanciones Laborales)

**Enrichments:**

* `ar_repet_person_enrichment` - Person labor sanctions data

<Expandable title="Data points provided">
  `addresses`, `aliases`, `dateOfBirth`, `documents`, `fullName`, `isCurrentPep`, `isPep`, `legalName`, `nationality`, `pepCountry`, `pepLevels`, `registrationNumber`, `sanctioned`, `sanctions`, `taxId`, `terrorismRegistryActive`, `terrorismRegistryMatch`, `terrorismRiskLevel`
</Expandable>

* `ar_repet_entity_enrichment` - Entity labor sanctions data

<Expandable title="Data points provided">
  `address`, `addresses`, `aliases`, `legalName`, `sanctioned`, `sanctions`, `terrorismRegistryActive`, `terrorismRegistryMatch`, `terrorismRiskLevel`
</Expandable>

#### ARCA / AFIP (taxpayer registry)

**Enrichments:**

* `ar_arca_contribuyente_enrichment` - AFIP taxpayer data via ARCA (registry A13 and tax certificate by CUIT/CUIL). Complements identity and tax status.

<Expandable title="Data points provided">
  `address`, `addresses`, `addressesSummary`, `city`, `country`, `dateOfBirth`, `firstName`, `fullName`, `idNumber`, `idType`, `incomeTaxCondition`, `incorporationDate`, `isAutonomous`, `isDeceased`, `isIvaRegistered`, `isMonotributo`, `ivaCondition`, `lastName`, `legalForm`, `legalName`, `mainActivityAfipCode`, `mainActivityAfipDescription`, `monotributoActivityDescription`, `monotributoCategory`, `postalCode`, `state`, `taxId`
</Expandable>

#### Gu1 (UIF, KIA, MiPyme/TIA, JIA, PIA/PEP)

AFIP-related and PEP compliance integrations for CUIT/CUIL (marketplace orchestration + ms-providers).

**Enrichments:**

* `ar_gueno_uif_enrichment` - UIF: obligated subjects and registration

<Expandable title="Data points provided">
  `isUifObligatedSubject`, `riskFlags`, `riskFlagsSummary`, `taxId`, `uifInscription`
</Expandable>

* `ar_gueno_kia_enrichment` - KIA compliance module (CUIT/CUIL)

<Expandable title="Data points provided">
  `address`, `addresses`, `addressesSummary`, `age`, `city`, `country`, `dateOfBirth`, `fullName`, `idNumber`, `idType`, `isDeceased`, `legalName`, `mainActivityAfipCode`, `mainActivityAfipDescription`, `postalCode`, `riskFlags`, `riskFlagsSummary`, `state`, `taxId`, `tipo`
</Expandable>

* `ar_gueno_tia_enrichment` - MiPyme / TIA (CUIT/CUIL)

<Note>
  Row-level TIA fields (`mipymeRows`, vigencias, flags de módulo) live in the **per-provider mapped** payload and raw response. The **consolidated** `normalized_enrichment` surface for rules/matrices includes **`taxId`** (subject of search) and **`isMyPyme`** (boolean from TIA). Keep `normalized-field-providers` in sync when adding new root keys.
</Note>

<Expandable title="Data points provided">
  `isMyPyme`, `taxId`
</Expandable>

* `ar_gueno_jia_enrichment` - AFIP “non-reliable” taxpayers (JIA)

<Note>
  Besides `taxId`, consolidated signals are exposed under `riskFlags` / `riskFlagsSummary`.
</Note>

<Expandable title="Data points provided">
  `riskFlags`, `riskFlagsSummary`, `taxId`
</Expandable>

* `ar_gueno_pia_enrichment` - PIA: compliance PEP (CUIT/CUIL)

<Note>
  Detail rows (`pepRows`, related CUIT, free-text fields) stay in the **per-provider mapped** payload. For **consolidated** `normalized_enrichment` / rules, the mapper promotes **`taxId`**, **`isPep`** / **`isCurrentPep`** (confirmed PEP, upstream code `1`), **`isPepPossible`** (possible PEP, code `2`), **`pepComplianceRowCount`**, plus **`riskFlags`** / **`riskFlagsSummary`** when hits exist.
</Note>

<Expandable title="Data points provided">
  `isCurrentPep`, `isPep`, `isPepPossible`, `pepComplianceRowCount`, `riskFlags`, `riskFlagsSummary`, `taxId`
</Expandable>

#### Renaper

**Enrichments:**

* `ar_renaper_validate_dni_enrichment` - DNI validation enrichment (identity flow)

<Note>
  `ar_renaper_validate_dni_*` codes are **not** listed in `normalized-field-providers` today (`getFieldsProvidedBy` returns no keys). They drive validation / session flows rather than consolidated normalized scalars in this catalog.
</Note>

* `ar_renaper_data_enrichment` - Person identity data from Renaper

<Expandable title="Data points provided">
  `address`, `addresses`, `addressesSummary`, `city`, `country`, `dateOfBirth`, `firstName`, `fullName`, `idNumber`, `idType`, `isDeceased`, `lastName`, `nationality`, `postalCode`, `state`, `taxId`
</Expandable>

### Chile (CL)

#### BaseAPI (SII)

**Enrichments:**

* `cl_baseapi_basic_data_person_enrichment` — Public SII taxpayer status by RUT (natural person). Routed via `ms-providers` KYB; the HTTP path includes `organizationId`.

* `cl_baseapi_basic_data_company_enrichment` — Same upstream SII response; use this code when the entity is a company.

<Expandable title="Data points provided (person)">
  `economicActivities`, `economicActivitiesSummary`, `fullName`, `incorporationDate`, `mainActivityAfipCode`, `mainActivityAfipDescription`, `registrationUptimeMonths`, `taxId`
</Expandable>

<Expandable title="Data points provided (company)">
  `economicActivities`, `economicActivitiesSummary`, `incorporationDate`, `legalName`, `mainActivityAfipCode`, `mainActivityAfipDescription`, `registrationUptimeMonths`, `taxId`
</Expandable>

<Note>
  Root keys `mainActivityAfipCode` / `mainActivityAfipDescription` are **shared consolidated field names**; for Chile they hold the **primary economic activity code and description** from SII (not Argentina AFIP).
</Note>

#### SRE (commercial registry)

**Enrichments:**

* `cl_sre_info_person_enrichment` — Minimal registry-style identity by RUT (person slot).

* `cl_sre_info_company_enrichment` — Same for companies.

<Expandable title="Data points provided (person)">
  `fullName`, `taxId`
</Expandable>

<Expandable title="Data points provided (company)">
  `legalName`, `taxId`
</Expandable>

#### ruts.info

**Enrichments:**

* `cl_rutsinfo_info_person_enrichment` — Commercial sheet data (activities, addresses) when available for the RUT.

* `cl_rutsinfo_info_company_enrichment` — Same for companies.

<Expandable title="Data points provided (person)">
  `addresses`, `addressesSummary`, `economicActivities`, `economicActivitiesSummary`, `fullName`, `incorporationDate`, `mainActivityAfipCode`, `mainActivityAfipDescription`, `taxId`
</Expandable>

<Expandable title="Data points provided (company)">
  `addresses`, `addressesSummary`, `economicActivities`, `economicActivitiesSummary`, `incorporationDate`, `legalName`, `mainActivityAfipCode`, `mainActivityAfipDescription`, `taxId`
</Expandable>

### Global

#### ComplyAdvantage

**Enrichments:**

* `global_complyadvantage_company_search_enrichment` - Company sanctions data

<Expandable title="Data points provided">
  `aliases`, `aliasesSummary`, `country`, `hasAdverseMedia`, `mediaMentions`, `mediaSummary`, `registrationCountry`, `riskFlags`, `riskFlagsSummary`, `sanctioned`, `sanctions`, `sanctionsSummary`
</Expandable>

* `global_complyadvantage_person_search_enrichment` - Person sanctions data

<Expandable title="Data points provided">
  `hasAdverseMedia`, `isCurrentPep`, `isPep`, `mediaMentions`, `mediaSummary`, `pepLevels`, `sanctions`, `sanctionsSummary`
</Expandable>

* `global_complyadvantage_sanctions_enrichment` - Complete sanctions records

<Expandable title="Data points provided">
  `registrationCountry`, `riskFlags`, `riskFlagsSummary`, `sanctioned`, `sanctions`, `sanctionsSummary`
</Expandable>

* `global_complyadvantage_pep_enrichment` - Global PEP profiles

<Expandable title="Data points provided">
  `isCurrentPep`, `isPep`, `pepLevels`
</Expandable>

#### Gu1 (global sanctions)

**Enrichments:**

* `global_gueno_sanctions_enrichment` - Gu1 global sanctions enrichment (incl. watchlist / monitoring when enabled)

<Expandable title="Data points provided">
  `riskFlags`, `riskFlagsSummary`, `sanctioned`, `sanctions`, `sanctionsSummary`
</Expandable>

## Usage Examples

### Execute Specific Integrations

```json theme={null}
{
  "autoExecuteIntegrations": {
    "enrichments": [
      "br_bdc_basic_data_enrichment",
      "br_bdc_shareholders_enrichment",
      "br_amldd_pep_enrichment",
      "global_complyadvantage_sanctions_enrichment"
    ]
  }
}
```

### Execute All Active Integrations

```json theme={null}
{
  "autoExecuteIntegrations": {
    "executeAllActiveEnrichments": true
  }
}
```

### Selective Integration for Shareholders

```json theme={null}
{
  "autoExecuteIntegrationsShareholders": {
    "enrichments": {
      "company": ["br_bdc_basic_data_enrichment", "br_bdc_kyc_business_enrichment"],
      "person": ["br_cpfcnpj_complete_person_enrichment", "br_amldd_pep_enrichment"]
    }
  }
}
```

## Provider Coverage by Country

| Country        | Providers                                                     | Enrichments (documented) |
| -------------- | ------------------------------------------------------------- | ------------------------ |
| Brazil 🇧🇷    | BDC, JusBrasil, AMLDD, CPF/CNPJ, BrasilAPI                    | 40+                      |
| Argentina 🇦🇷 | BCRA, Nosis, REPET, ARCA/AFIP, Gu1 (UIF/KIA/TIA/JIA), Renaper | 12+                      |
| Global 🌍      | ComplyAdvantage, Gu1 sanctions                                | 6                        |

## Best Practices

1. **Prefer enrichments**: Use the enrichment codes listed here for execution configuration.
2. **Use `executeAllActiveEnrichments`**: Let the platform determine which integrations to run based on your configuration.
3. **Be specific for shareholders**: Use selective integration for shareholders to control costs.
4. **Combine providers**: Mix different providers for comprehensive coverage.
5. **Consider costs**: Some providers are heavier than others; scope integrations to what you need.

## Related Documentation

* [Create Entity](/api-reference/entities/create) - Using provider codes in manual creation
* [Create Entity Automatically](/en/api-reference/entities/create-automatic) - Using provider codes in automatic creation
* [Integration Execution](/en/api-reference/integrations/execute-without-entity) - Execute integrations on existing entities