How We Source Hong Kong Registry Data
Trusgent publishes machine-readable copies of Hong Kong official registers so search engines and AI agents can cite licence and registration facts with clear provenance. The official register always remains authoritative.
1. Acquisition
We import published open datasets (primarily data.gov.hk) and authority exports such as Insurance Authority broker/agency lists. Each source maps to a known issuing authority, dataset URL, and official verification channel.
2. Cleaning & Indexing
Raw rows are normalized into a shared schema: bilingual names where available, licence numbers, addresses, districts, licence types, and stable registry IDs (e.g. fehd-…, iaag-…). Placeholder or empty names are not invented.
3. Sync & “Last Verified”
“Last Verified” on entity pages is the date we last successfully synced that record from the upstream open data or export — not a live government API call at page view. Information may lag; always confirm critical decisions on the official register.
4. Claim ≠ Verified
Claiming binds an Agent Card to a registry row. It does not mean the business is identity- or licence-verified on Trusgent. Verification requires the paid human review flow and updates Trust Score only after approval.
5. Enrichment Layers
Optional fields such as phone or opening hours appear in structured data only when merchant-confirmed via our enrichment pipeline. Unconfirmed third-party scrape data is never presented as official.
6. Machine Access
Every /r page exposes JSON-LD, REST JSON (/api/v1/registry/…), and MCP tools. Citations include issuer, dataset link, sync date, and verify URL so agents can attribute the source.