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

# KGC Compliance

> How Currents satisfies Anunnaki's Kahnawake regulatory obligations — and why tenants get coverage automatically.

Anunnaki Elite operates under a Kahnawake Gaming Commission (KGC) Client Provider Authorisation (permit **#1039**). Several KGC obligations require ongoing reporting of player-protection activity across **every** KGC-licensed brand. Currents implements these centrally so that each operator (tenant) inherits compliance simply by using the standard APIs.

<Note>
  You do not call any special "compliance" endpoint to be covered. Keep using the documented Self-Exclusion and Deposit Limits APIs — the regulatory ingest and reporting run on Anunnaki's side.
</Note>

## The three obligations

| Obligation                    | What it covers                                                                                         | How Currents satisfies it                                                                                                                                          |
| ----------------------------- | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Self-exclusion**            | The KGC comprehensive master self-exclusion list must block listed players across all licensed brands. | The master list is ingested centrally and matched **cross-tenant by default** at [`GET /v1/exclusions/check`](/api-reference/self-exclusion).                      |
| **\$10,000 threshold (s.28)** | Any transaction or series of transactions over USD 10,000 in a defined window must be reported.        | Detected from the transactions you already stream to the [AML API](/api-reference/aml) (rules **R-001** and **R-009**) and compiled into the KGC threshold report. |
| **Self-limitations (s.229A)** | Player-set self-limits (deposit caps, etc.) and their changes must be reported regularly.              | Every change made through the [Deposit Limits API](/api-reference/deposit-limits) is recorded and compiled into the KGC self-limitation report.                    |

## How you get coverage

<Steps>
  <Step title="Stream events as documented">
    Keep calling Self-Exclusion, Deposit Limits, and AML (`POST /v1/aml/event`) exactly as described in their reference pages. No extra fields, no extra calls.
  </Step>

  <Step title="Cross-brand enforcement is automatic">
    KGC master-list exclusions are matched on every `check` regardless of tenant, so a player excluded on one brand is blocked on all of them.
  </Step>

  <Step title="Reporting happens centrally">
    Anunnaki compiles and files the threshold (s.28) and self-limitation (s.229A) reports from the data you've already sent. Nothing for you to generate or submit.
  </Step>
</Steps>

## What this does *not* change for you

* **No new request/response shapes.** The compliance coverage is additive and invisible at the API surface.
* **No tipping-off risk.** As with AML, never surface compliance internals (rule codes, report status, master-list membership) to end users — use neutral language only.
* **Report generation is internal.** The admin ingest and report-export tooling is operated by Anunnaki and is intentionally **not** part of this public reference.

<Note>
  Questions about your brand's KGC coverage? Contact Anunnaki compliance via your integration manager.
</Note>