Skip to content

Getting started

Welcome to the MasteryHive platform documentation.

MasteryHive provides AI-assisted risk, compliance, and finance automation that banking and fintech applications call over HTTP and event-driven interfaces. This site explains what the products do, how partners integrate, and (on the internal site) how engineers operate and extend them.

Supported products

Product What it does
Fraud Detection Behavioural baselines, ML/rule scoring, investigator-facing AI reports
KYC / KYB (AML) Identity, documents, biometrics, sanctions/PEP/adverse media, risk scoring
Banking Reconciliation Statement ↔ GL / asset matching, exceptions, and resolve workflows

Case management (rule scoring for case-oriented decisioning) and regulatory reporting helpers (for example goAML XML generation) are covered under Fraud and KYC respectively — see the platform overview.

Who this documentation is for

Audience Start here
Evaluators / product stakeholders Platform overview · journey Evaluate MasteryHive
Partner / client engineers Integration · Auth and tenancy · journey Integrate KYC
Operations / support Product reliability pages · journey Operate Fraud (deep runbooks are internal)
MasteryHive engineers Join the engineering team (full Engineering section on the internal site)

Prerequisites

Before calling APIs in a shared environment you typically need:

  1. Agreement with MasteryHive on which products and which environment you will use.
  2. Authentication material for that environment (for Fraud scoring: bidirectional JWT key exchange; for other products: environment-specific gateway or network controls — see Auth and tenancy).
  3. Tenant / partner / user identifiers as required by each product.
  4. Access to test data and a non-production environment when available.

Exact provisioning steps: Access and credential onboarding. Environment names: Environments.

Use the audience journeys for step-by-step paths. A short default path for most new readers:

  1. Platform overview
  2. System map
  3. The product page for your use case
  4. Integration and the matching API guide
  5. Glossary when terms collide

What is public vs internal

This public site publishes Getting Started, Products, Integration, API Reference, and high-level Architecture. Engineering runbooks, ADRs, findings, and operator depth live on the internal documentation site. See the documentation map.