Data Licensing
Coming Q3 2026

Regulation, Rendered as Structured Data.

Every obligation parsed, classified by deontic type, and tied to legal citation, source text, and page. The register powers our live dashboard today. Tiered API licensing for third parties opens Q3 2026.

6,000+
Obligations
3
Regulations
SG / PH
Coverage
Obligation Register
BSP.MORB.PartIX.2023.Sec903.OBL1SHALLOBLIGATIONCriminal

Covered persons shall establish and record the true identity of their customers based on official documents.

MORB Part IX, Sec. 903, p. 412 (2023)Customer IdentificationCDD/KYC
BSP.MORB.PartIX.2023.Sec903.PRH1SHALL NOTPROHIBITIONCriminal

Covered persons shall not open or maintain anonymous accounts or accounts in fictitious names.

MORB Part IX, Sec. 903, p. 416 (2023)Customer IdentificationCDD/KYC
BSP.MORB.PartIX.2023.Sec904.REC1SHOULDRECOMMENDATION

Covered persons should categorise customers into low-, normal-, and high-risk profiles based on documented criteria.

MORB Part IX, Sec. 904, p. 423 (2023)Risk-Based ApproachRisk-Based
BSP.MORB.PartIX.2023.Sec906.PRM1MAYPERMISSIONCriminal

A covered person may delay execution of a suspicious transaction in coordination with the AMLC pursuant to Sec. 906(c).

MORB Part IX, Sec. 906(c), p. 441 (2023)Suspicious TransactionsMonitoring
MAS.TRM.2021.Sec3.1.OBL1SHALLOBLIGATION

The board of directors shall ensure that a sound and robust technology-risk-management framework is established and maintained.

MAS TRM, Sec. 3.1, p. 12 (2021)Technology Risk GovernanceGovernance
MAS.TRM.2021.Sec8.4.PRH1SHALL NOTPROHIBITION

The use of obsolete or weakened cryptographic algorithms shall not be permitted in production systems.

MAS TRM, Sec. 8.4, p. 67 (2021)Cryptographic ControlsSecurity
MAS.TRM.2021.Sec8.4.REC1SHOULDRECOMMENDATION

Cryptographic keys should be rotated at intervals commensurate with the sensitivity of the data they protect.

MAS TRM, Sec. 8.4, p. 70 (2021)Cryptographic ControlsSecurity
AMLC.GoTRACS.2024.Sec4.OBL1SHALLOBLIGATIONCriminal

Covered persons shall report covered transactions exceeding the threshold to the AMLC within the prescribed reporting period.

AMLC GoTRACS, Sec. 4, p. 18 (2024)Covered Transaction ReportingReporting
AMLC.GoTRACS.2024.Sec6.PRH1SHALL NOTPROHIBITIONCriminal

Covered persons shall not warn or notify a customer that a suspicious transaction report has been or is being filed.

AMLC GoTRACS, Sec. 6, p. 27 (2024)Confidentiality of ReportingMonitoring
AMLC.GoTRACS.2024.Sec9.OBL1SHALLOBLIGATION

Covered persons shall retain all transaction records and customer identification documents for at least five (5) years.

AMLC GoTRACS, Sec. 9, p. 41 (2024)Record RetentionRecordkeeping
BSP.MORB.PartIX.2023.Sec903.OBL1SHALLOBLIGATIONCriminal

Covered persons shall establish and record the true identity of their customers based on official documents.

MORB Part IX, Sec. 903, p. 412 (2023)Customer IdentificationCDD/KYC
BSP.MORB.PartIX.2023.Sec903.PRH1SHALL NOTPROHIBITIONCriminal

Covered persons shall not open or maintain anonymous accounts or accounts in fictitious names.

MORB Part IX, Sec. 903, p. 416 (2023)Customer IdentificationCDD/KYC
BSP.MORB.PartIX.2023.Sec904.REC1SHOULDRECOMMENDATION

Covered persons should categorise customers into low-, normal-, and high-risk profiles based on documented criteria.

MORB Part IX, Sec. 904, p. 423 (2023)Risk-Based ApproachRisk-Based
BSP.MORB.PartIX.2023.Sec906.PRM1MAYPERMISSIONCriminal

A covered person may delay execution of a suspicious transaction in coordination with the AMLC pursuant to Sec. 906(c).

MORB Part IX, Sec. 906(c), p. 441 (2023)Suspicious TransactionsMonitoring
MAS.TRM.2021.Sec3.1.OBL1SHALLOBLIGATION

The board of directors shall ensure that a sound and robust technology-risk-management framework is established and maintained.

MAS TRM, Sec. 3.1, p. 12 (2021)Technology Risk GovernanceGovernance
MAS.TRM.2021.Sec8.4.PRH1SHALL NOTPROHIBITION

The use of obsolete or weakened cryptographic algorithms shall not be permitted in production systems.

MAS TRM, Sec. 8.4, p. 67 (2021)Cryptographic ControlsSecurity
MAS.TRM.2021.Sec8.4.REC1SHOULDRECOMMENDATION

Cryptographic keys should be rotated at intervals commensurate with the sensitivity of the data they protect.

MAS TRM, Sec. 8.4, p. 70 (2021)Cryptographic ControlsSecurity
AMLC.GoTRACS.2024.Sec4.OBL1SHALLOBLIGATIONCriminal

Covered persons shall report covered transactions exceeding the threshold to the AMLC within the prescribed reporting period.

AMLC GoTRACS, Sec. 4, p. 18 (2024)Covered Transaction ReportingReporting
AMLC.GoTRACS.2024.Sec6.PRH1SHALL NOTPROHIBITIONCriminal

Covered persons shall not warn or notify a customer that a suspicious transaction report has been or is being filed.

AMLC GoTRACS, Sec. 6, p. 27 (2024)Confidentiality of ReportingMonitoring
AMLC.GoTRACS.2024.Sec9.OBL1SHALLOBLIGATION

Covered persons shall retain all transaction records and customer identification documents for at least five (5) years.

AMLC GoTRACS, Sec. 9, p. 41 (2024)Record RetentionRecordkeeping
  • 3Regulations Parsed
  • 2Jurisdictions · SG / PH
  • 6,000+Obligations Indexed
  • 100%Verbatim Provenance

The Data Model

Four Tiers of Access Over One Obligation Graph.

Each tier inherits everything below it and adds a layer of structure. License the depth your systems need, from raw extracts to drafted policy.

01Tier

Canonical Obligation Extract

The atomic record. One row per obligation, traceable to source.

Fields

verbatim_textlegal_citationpage_referenceregulation_id
02Tier

Contextual Obligation Set

The obligation in its document context, with the section hierarchy and cross-references.

Adds

context_windowsection_pathcross_references
03Tier

Policy Group Bundles

Obligations grouped by domain and mapped to control frameworks.

Adds

policy_groupframework_tagscrosswalk_data
04Tier

AI Policy Statements

Ready-to-adopt policy wording at obligation and group level. Full drafted policies where applicable.

Adds

policy_statementfull_policy_draft+All Tier Data

Audit-Grade by Construction

Every Obligation Traces Back
to the Page It Came From.

Extraction is verbatim and deterministic, not summarized. Every record in the dataset includes the evidence a compliance team and an auditor need to trust it without re-reading the source regulation.

Verbatim Text

Exact obligation wording as published, never paraphrased.

Legal Citation and Page

Section, clause, and page number for direct lookup.

Source Screenshot

Image of the page with the obligation text highlighted by bounding box.

Extraction Timestamp

ISO timestamp of when the obligation was extracted from source, for audit trail and version control.

Licensing

Coming Q3 2026

Priced by Tier and Coverage.

Annual API subscription per regulation, or a discounted bundle across all three. API licensing opens Q3 2026. Starting figures in USD are indicative and set per counterparty at contract.

Canonical ExtractT01

Verbatim text, citation, page, regulation id.

API + CSV

Single Regulation

Starting from$8,000/ yr

Multiple Regulations

Starting from$18,000/ yr
Contextual SetT02

Adds document context and cross-references.

API + CSV

Single Regulation

Starting from$15,000/ yr

Multiple Regulations

Starting from$35,000/ yr
Policy Group BundlesT03

Grouped by domain, framework-mapped.

API + CSV

Single Regulation

Starting from$25,000/ yr

Multiple Regulations

Starting from$55,000/ yr
AI Policy StatementsT04Premium

Ready-to-implement policy language. Living content.

API

Single Regulation

Starting from$45,000/ yr

Multiple Regulations

Starting from$100,000/ yr

Enterprise and OEM Embedding

Embed the obligation layer in your own platform under a flat annual license or revenue share.

Starting from$150,000 / yr

One-time data pulls available for Tiers 01 to 03. Update cadence set by SLA.

Delivery

Built for the Systems That Consume It.

  • REST API, JSON Native

    Query obligations by regulation, policy group, or citation. Stable identifiers across versions.

  • CSV Flat Files

    Bulk delivery for warehouses and pipelines that prefer tabular ingestion.

  • Versioned and Timestamped

    Every record is version-tagged. Amendment and supersession tracked where the regulator publishes it.

Sample Data

Representative excerpt. Full obligation records include additional fields.

GET/v1/regulatory/obligations/BSP.MORB.PartIX.2023.Sec903.OBL1
{
  "obligation_id": "BSP.MORB.PartIX.2023.Sec903.OBL1",
  "obligation_group_id": "BSP.MORB.PartIX.2023.Sec903.OBL.GRP.01",
  "deontic": "OBLIGATION",
  "parsed_requirement": {
    "modal": "SHALL",
    "modal_strength": "mandatory",
    "deontic_category": "obligation",
    "matched_keyword": "shall",
    "is_negative": false
  },
  "obligation_type": "process",
  "covered_person_scope": ["all"],
  "is_criminal_offense": true,
  "verbatim_text": "Covered persons shall establish and record the true identity of their customers based on official documents.",
  "source": {
    "jurisdiction": "Philippines",
    "regulator": "Bangko Sentral ng Pilipinas (BSP)",
    "document_title": "Manual of Regulations for Banks",
    "document_version": "2023",
    "framework": "MORB",
    "section_number": "903",
    "section_title": "Customer Identification",
    "legal_citation": "MORB, Sec. 903, p. 412 (2023 ed.)",
    "page_number": 412,
    "page_start": 412,
    "page_end": 412,
    "extraction_timestamp": "2026-06-17T10:05:38.073911+00:00",
    "ocr_confidence": 0.99
  },
  "last_updated": "2026-06-17T10:05:38.073911+00:00"
}
  

Register Interest

Coming Q3 2026

Get on the Early-Access List.

API licensing opens Q3 2026. Register now and we will reach out to discuss tiers, coverage, and indicative pricing for your use case.

Step 01

We Reach Out

A member of the team will contact you within two business days to discuss your use case.

Step 02

Scope and Tiers

We walk through coverage, delivery options, and indicative pricing for your needs.

Step 03

Early Access

Priority notification and onboarding when API licensing opens in Q3 2026.