> ## Documentation Index > Fetch the complete documentation index at: https://developers.fireblocks.com/llms.txt > Use this file to discover all available pages before exploring further. # AML/KYT Overview > How Fireblocks screens incoming and outgoing transactions for blockchain risk through Chainalysis, Elliptic, or TRM Labs, which provider to choose, and the API endpoints you work with. AML/KYT screens your incoming and outgoing transactions against blockchain risk data, checking for connections to activity such as sanctions, darknet markets, stolen funds, or ransomware. Fireblocks sends each matching transaction to your AML/KYT provider, receives a risk assessment, and applies your policy's action before the transaction continues. It runs after [Address Registry Screening](/docs/address-registry-screening) and before [Travel Rule](/docs/travel-rule-overview). AML/KYT checks any address against your provider's risk data, regardless of whether the counterparty is a Fireblocks customer. Address Registry Screening checks whether an address belongs to a verified entity on the Fireblocks network. You can use both in the same policy. The provider assesses risk; your policy decides what happens. Neither replaces your compliance program: you remain responsible for reviewing flagged transactions and filing any required reports. AML/KYT screening flow ## Providers AML/KYT is a premium add-on: Fireblocks Support enables it on your workspace, and you connect your provider in the Console. Each provider has its own guide that covers what it sends and returns, its timeouts, and the assets it supports. | Provider | Risk result | Workspaces | | - | - | - | | [Chainalysis](/docs/chainalysis) | Categorical risk level, plus the risk category matched | Testnet, Mainnet | | [Elliptic](/docs/elliptic) | Numeric risk score | Mainnet | | [TRM Labs](/docs/trm-labs) (Early Access) | Categorical risk level, plus the risk categories matched | Mainnet | Only one AML/KYT provider can be connected to a workspace at a time, but different workspaces can use different providers. Connecting and disconnecting are not available through the API: to switch or disconnect, contact Fireblocks Support. To pause transactions for your own review, regardless of the review process or provider, see [Bring Your Own Screening](/reference/bring-your-own-screening-check-developer-guide). ## Working with AML/KYT through the API | Task | Endpoint | Guide | | - | - | - | | Read the Trigger (Screening Policy) and Outcome (Post-Screening Policy) | [`GET /screening/aml/screening_policy`](/api-reference/compliance/aml--view-screening-policy), [`GET /screening/aml/post_screening_policy`](/api-reference/compliance/aml--view-post-screening-policy) | [Compliance Policies](/docs/compliance-policies) | | Configure outage and delay behavior | [`PUT /screening/aml/policy_configuration`](/api-reference/compliance/update-aml-configuration) | [Compliance Policies](/docs/compliance-policies#configure-outage-and-delay-behavior) | | Attribute transactions to a customer | [`POST /vault/accounts/{vaultAccountId}/set_customer_ref_id`](/api-reference/vaults/set-an-amlkyt-id-for-a-vault-account) | [Customer Reference ID](/docs/customer-reference-id) | | Read a transaction's AML/KYT result | [`GET /screening/transaction/{txId}`](/api-reference/compliance/provides-all-the-compliance-details-for-the-given-screened-transaction), in the `aml` and `amlList` fields | [Transaction Screening Operations](/docs/transaction-screening-operations) | | Bypass, rescreen, freeze, or unfreeze | See the guide | [Transaction Screening Operations](/docs/transaction-screening-operations) | ## Limitations * **Coverage varies by provider.** Which blockchains and assets a provider can screen depends on that provider's data coverage, not on Fireblocks. * **Some routes are not screened:** vault account to vault account, vault account to exchange, Gas Station to vault account, and non-custodial wallet to non-custodial wallet within the same workspace. Outgoing transactions on these routes still go through your provider's registration flow, so they can count toward your usage quota. To avoid this, add a Pass rule for them. ## On the Help Center To connect a provider or build AML/KYT rules in the Console, see [About AML/KYT](https://support.fireblocks.io/hc/en-us/articles/30614362833308-About-AML-KYT).