Global Ledger Product Guide
Global Ledger: GLO Services AG, Grafenauweg 8, 6300 Zug, Switzerland.
Document version: 12.10.2026
This Product Guide forms part of the Documentation under Section 3.2 of the MSA and describes the Services available under an Order. Global Ledger may update this Product Guide, subject to the Agreement and, for changes to Request consumption, the procedure in Annex A. Capitalised terms used but not defined here have the meanings given in the MSA. The MSA’s order of precedence applies in the event of a conflict.
Fees, list prices, discounts and the Overage Fee for each Service are set forth in the applicable Order. This Product Guide does not contain pricing.
1. Definitions
“Package” means the set of Features and the Quantity purchased by Customer, as specified in an Order.
“Add-on” means any additional Features or Quantity purchased by Customer in addition to a Package, as specified in an Order.
“Feature” means a functional component of the Services listed in Section 3 (Feature Catalogue). A Feature is available to Customer only if it is included in the Package or Add-on specified in an Order.
“Request” means the unit in which Customer’s use of the Services is measured. Each action performed through the Services, whether initiated through the user interface (“UI”), the application programming interface (“API”) or an automated process (including Monitoring), consumes the number of Requests specified for that action in Annex A (Request Consumption), which may be zero. Global Ledger may verify compliance with the agreed Request limits in accordance with Section 3.7.1 of the MSA.
“User” has the meaning given in Section 3.7.1 of the MSA.
“Quantity” means the permitted number of Requests and the User capacity for a Package or Add-on, as specified in an Order. Request allocation periods and User capacity are subject to Section 4.1.3 of the MSA.
“Supported Blockchains” means the blockchain networks and digital assets supported by the Services from time to time, at the coverage tier (Advanced or Essential) specified for each network in the Documentation.
“Documentation” has the meaning given in Section 3.2 of the MSA.
2. General Terms Applicable to All Packages and Add-ons
2.1 Quantity and Request Consumption
The Quantity of Requests is specified in the Order. Requests are consumed at the same rate whether an action is performed through the UI or API. Repeated actions in respect of the same address, transaction or entity, and actions performed by automated processes enabled by Customer, including the addition of an address to Monitoring and each new transaction of a monitored address, consume Requests as specified in Annex A.
2.2 Users
The number of Users specified in the Order applies across UI and API access. A User accessing both channels counts as one User. Each User requires a named account; account credentials shall not be shared. Customer’s organisation administrator may reassign access after the former User loses access. Global Ledger issues an API key to each User. The key may be used by Customer’s authorised systems and in integrations and partner platforms documented by Global Ledger in advance. Customer remains responsible for securing the key and ensuring compliance with the agreed usage limits.
2.3 Unlimited Packages
Where an Order specifies an “Unlimited” Quantity of Requests, “Unlimited” refers only to the number of Requests and does not extend to User capacity, API concurrency or other limits specified in the Order or Documentation.
2.4 Supported Blockchains and Coverage Tiers
All Packages and Add-ons include access to all Supported Blockchains. The depth of data, Features and analysis available for a given blockchain network depends on its coverage tier (Advanced or Essential) as set forth in the Documentation; certain Features (including Monitoring and Alerts, Custom Scoring Profiles, Entity Report and DeFi Report) may be available only for networks at the Advanced tier; alerts configured for Risk Reports are available for all Supported Blockchains. Supported networks, coverage tiers and the depth and historical range of available blockchain data may change over time.
2.5 AI-Assisted Features
The Risk Report includes AI-assisted output in all Packages. AI-assisted output is generated only following an affirmative request by a User through the Risk Report interface. The underlying risk data, attribution and scoring are produced by Global Ledger’s data and analytics; the natural-language output is automated and may contain inaccuracies or omissions. AI-generated output is provided for informational purposes to assist Customer’s review and does not constitute a compliance determination, legal advice or a recommendation. Customer remains solely responsible for any decision taken on the basis of the Services.
2.6 API Access
Where a Feature is identified as “+API” in Section 3 and the Order provides for API access, Customer may access that Feature through the API in accordance with the Documentation, subject to the Quantity and to reasonable technical rate limits, details of which are available from Global Ledger on request. Features not identified as “+API” are available through the UI only.
2.7 GL-Lens Browser Extension
The GL-Lens Extension may be used only by authorised Users where it is included in the Package or Add-on specified in the Order. Use of the GL-Lens Extension does not itself consume Requests; a Risk Report generated from the GL-Lens Extension consumes Requests in the same way as any other Risk Report. The GL-Lens Extension is subject to the terms of the browser store through which it is distributed.
2.8 Automated Processes
Monitoring and Auto Tracing operate continuously once enabled by Customer and perform actions without further input from Customer. Actions performed by such automated processes consume Requests in the same manner as actions initiated by Customer (Section 2.1). Customer is responsible for the addresses and transactions it designates and for disabling any automated process it no longer requires.
2.9 Custom Scoring Profiles
Custom Scoring Profiles allow Customer’s organisation administrator to change the risk scores assigned to the types and tags used in risk scoring. A Custom Scoring Profile applies to all users of Customer’s organisation and is available only for blockchain networks at the Advanced tier (Section 2.4). Risk scores produced under a Custom Scoring Profile reflect Customer’s own configuration and may differ from those produced under Global Ledger’s default scoring profile. Customer is solely responsible for the configuration of its Custom Scoring Profiles and for any decision taken on their basis.
3. Feature Catalogue
The following Features may be included in an Order. “UI” indicates availability through the user interface; “+API” indicates that the Feature is additionally available through the API; “+AI” indicates that the Feature includes AI-assisted output (Section 2.5). The Features available to Customer, including any API access and AI-assisted output, are as specified in the Order.
|
Feature |
Description |
Channels |
|---|---|---|
|
Dashboard |
Overview of Customer’s screening, monitoring and case activity. |
UI |
|
Risk Report |
Risk assessment of an address or transaction, including exposure to sanctions, scams, hacks and other illicit or high-risk activity. |
UI; +API where specified in the Order |
|
Screening Report (not yet available; until its general release, Screening Report does not form part of the Services) |
Label-based screening of an address or transaction against Global Ledger attribution data, without fund-flow tracing. Available from the general release of the Feature (see note below). |
UI; +API where specified in the Order |
|
Monitoring and Alerts |
Continuous monitoring of designated addresses and generation of alerts based on configured rules. |
UI; +API where specified in the Order |
|
History |
Record of Customer’s previous Requests and reports. |
UI |
|
Custom Scoring Profiles |
Customer-configurable risk weighting (Section 2.9). |
UI |
|
KYT Lab |
Early-access analytical capabilities made available from time to time; provided “as is” and may be modified or withdrawn. |
UI |
|
Visual Tracing Tool (Tracing) |
Multi-hop visualisation of fund flows, entity clustering and service attribution. |
UI |
|
Case Management (Case Files) |
Creation, collaboration on and export of investigation cases and evidence. |
UI |
|
Auto Tracing |
Automated continuous tracing of the path of funds from a designated origin (Section 2.8). |
UI |
|
GL-Lens Extension (GL Lens) |
Browser extension surfacing Global Ledger risk data on third-party web pages (Section 2.7). |
Google Chrome Extension |
|
Entity Database |
Access to Global Ledger’s database of attributed crypto entities (VASPs, services, merchants and other organisations). |
UI; +API where specified in the Order |
|
Entity Report |
Report on an entity’s incoming and outgoing exposure for a Customer-selected period, with transaction-level detail. Generation of each Entity Report consumes one hundred (100) Requests. |
UI |
|
DeFi Report |
Report on decentralised-finance activity and exposure of a smart contract or liquidity pool. Generation of each DeFi Report consumes one hundred (100) Requests. |
UI |
Note: Screening Report is scheduled for general release and is not available as at the date of this Product Guide. Until its general release, Screening Report does not form part of the Services, and its unavailability shall not constitute a breach of the Agreement.
Annex A – Request Consumption
The number of Requests consumed by each action is set out in the table below. Requests are consumed at the same rate whether an action is performed through the UI or the API.
|
Feature |
Action |
Requests consumed |
|---|---|---|
|
Risk Report |
Generate a Risk Report for an address or a transaction |
1 |
|
Risk Report |
Re-generate a Risk Report for the same address (on the same or another blockchain) |
1 |
|
Risk Report |
Change the token for a Risk Report |
1 |
|
Risk Report |
Generate a PDF Risk Report |
1 |
|
Risk Report |
Generate a Risk Report for an address that is in Monitoring |
0 |
|
Risk Report |
Failed Risk Report request (no report produced). A Risk Report that returns no labels or exposure is a completed report and consumes 1 Request |
0 |
|
Monitoring and Alerts |
Add an address to Monitoring (including re-adding a previously removed address) |
10 |
|
Monitoring and Alerts |
Each new incoming or outgoing transaction of a monitored address |
1 |
|
Monitoring and Alerts |
Remove an address from Monitoring |
0 |
|
Monitoring and Alerts |
Create an alert for an address that is not in Monitoring (the address is added to Monitoring) |
10 |
|
Monitoring and Alerts |
Create an alert for an address that is already in Monitoring, or an alert applying to Risk Reports or to Monitoring generally |
0 |
|
Monitoring and Alerts |
Alert triggered; set-up of Slack, Telegram or Jira integrations for alerts |
0 |
|
History |
Any action |
0 |
|
KYT Lab |
Any action |
0 |
|
Visual Tracing Tool |
Any action |
0 |
|
Auto Tracing |
Any action |
0 |
|
Case Management |
Any action |
0 |
|
Entity Database |
Any action |
0 |
|
Entity Report |
Generate a report |
100 |
|
DeFi Report |
Generate a report |
100 |
|
Screening Report |
Generate a Screening Report for an address or a transaction |
1 |
|
GL-Lens Extension |
Use of the extension (a Risk Report generated from the extension consumes Requests as a Risk Report) |
0 |
Actions not listed above do not consume Requests. Global Ledger may update the Request consumption rules. Each update shall state its effective date and apply only to actions performed on or after that date. Changes that do not materially reduce the functionality of an ordered module may take effect without prior notice. For changes that materially reduce that functionality, Global Ledger shall give written notice as early as reasonably practicable before the change. Notice may be shorter, simultaneous or given promptly afterwards where immediate action is reasonably required on grounds permitted by the Agreement. Agreed Order entitlements and Customer’s rights and remedies under the Agreement remain unaffected.