MarketGuard primary sources — 2026-05-01

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is MarketGuard’s official homepage, help-center workflow docs, and the OpenAPI spec linked from the API reference.
• The public materials consistently frame MarketGuard as a compliance workspace for VASPs and blockchain businesses, not merely as a single AML-screening endpoint.

Primary-source snapshots

1) Official homepage

• URL: https://marketguard.io/
• Key excerpt:
  • The homepage presents MarketGuard as a “Plug-and-play AML & KYC solution for VASPs and CASPs.”
  • It says the product was “Created by a financial institution for financial institutions.”
  • It highlights KYC & KYB onboarding, transaction monitoring, integrated banks and custodians, secure data storage, customizable workflows, and regulatory reporting.

2) Help-center overview

• URL: https://help.marketguard.io/
• Key excerpt:
  • The overview says MarketGuard is an AML compliance solution for blockchain companies and VASPs.
  • It summarizes the platform around onboarding, ongoing monitoring, risk profiling, transaction monitoring, case management, and regulatory reporting.
  • This page was the clearest high-level source for recovering the full compliance workflow.

3) Client onboarding page

• URL: https://help.marketguard.io/marketguard/client-onboarding
• Key excerpt:
  • The docs say MarketGuard collects company and shareholder data for verification and supports identity checks via SMS, video identification, video-selfie, and photo-selfie.
  • It also highlights continuous monitoring against sanctions, PEP, and custom watchlists plus wallet verification and custom workflow statuses.
  • The page notes that trusts and foundations are not supported in the documented legal-entity workflow.

4) Client risk profiling page

• URL: https://help.marketguard.io/marketguard/client-risk-profiling
• Key excerpt:
  • The page says compliance officers can create AML quizzes for retail and business clients, with unlimited questions and scored responses.
  • It explains that customer risk scores drive assignment of normal, medium, or high-risk levels and allow officers to define customer-specific limits.
  • This is a strong clue that MarketGuard is packaging workflow logic for compliance teams, not only outsourced screening.

5) Transaction monitoring (KYT) page

• URL: https://help.marketguard.io/marketguard/transaction-monitoring-kyt
• Key excerpt:
  • The page says linked transactions are processed by a KYT module and high-risk transactions or transaction groups become formal cases.
  • It lists the main triggers as daily volume limits, 30-day rolling volume limits, blockchain-risk scores from a third-party scoring provider, country-risk checks, and payment-country checks.
  • This confirms that the operational core is case generation and review workflow rather than passive analytics alone.

6) API reference index

• URL: https://help.marketguard.io/api-reference
• Key excerpt:
  • The API reference currently exposes at least Transactions and Addresses sections.
  • Even though the public docs surface is not broad, it shows that MarketGuard has a machine-ingestion layer alongside the GUI workflow.

7) Transactions API page and OpenAPI spec

• URL: https://help.marketguard.io/api-reference/transactions
• Key excerpt:
  • The docs page links to an OpenAPI document whose production server is https://api.finchguard.com/.
  • The POST /api/v1/transactions endpoint accepts amount, asset/network, source addresses, destination address, optional transaction hash, payload, fee, venue metadata, and creation time.
  • The returned transaction model includes internal UID, source/destination address UIDs, transaction type, direction, amount, asset details, fee data, venue data, and timestamps; the same spec also exposes a paginated GET /api/v1/transactions endpoint.
  • The lingering finchguard server name is a useful note for future researchers because it suggests backend/product lineage continuity beneath the MarketGuard brand.

Working conclusion

MarketGuard is best cataloged as a crypto-compliance operations control plane centered on onboarding, risk profiling, KYT case generation, and reporting workflows for VASPs. The most useful differentiator in this pass was the combination of GUI-oriented compliance docs and a small but concrete ingestion API, which together show that the product is designed to operationalize AML/KYC/KYT work rather than only score wallets.