WeLab

WeLab is a Hong Kong-headquartered fintech group founded in 2013 (incorporated November 2012 as WeLend) by Simon Loong, Kelly Wong and Frances Kang, operating consumer lending, digital banking and payments businesses across Hong Kong, mainland China and Indonesia. Its brands include WeLend (Hong Kong online lending), WeLab Digital and Taoxinji (mainland China), WeLab Pay, Tianmian Lab, and two licensed digital banks — WeLab Bank Limited, one of Hong Kong's virtual banks licensed by the Hong Kong Monetary Authority in April 2019 and launched to the public in July 2020, and Bank Saqu (formerly Bank Jasa Jakarta) in Indonesia. WeLab Bank is the group's API-bearing entity: under the HKMA Open API Framework it publishes an "Open API" developer portal for registered third-party service providers, backed by dedicated production and sandbox API gateways that require a client certificate (mutual TLS) before any request is served. Investors across its funding rounds include Sequoia Capital, Alibaba Entrepreneurs Fund, Credit Suisse and Allianz.

WeLab is listed with 1 API on the APIs.io network. Tagged areas include Fintech, Digital Banking, virtual-bank, Open Banking, and Hong Kong.

WeLab’s developer surface includes support, engineering blog, authentication, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

19.4/100 emerging ▬ flat Agent 3/100 human only saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessApproval

1 API

Fintech Digital Bankingvirtual-bankOpen Banking Hong Kong Indonesia Consumer Lending Paymentshkma-open-apiFinancial Services

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 19.4/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 4.9 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.7 / 9

Regulatory Posture 3.7 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/welab/"><img src="https://apis.io/badge/welab/card.svg" alt="WeLab on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Developer Ergonomics scores 28.6 — up to +14.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/welab/apis.yml: open an issue on github.com/api-evangelist/welab to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Southeast Asia and National Fintech Registers (Taiwan, UAE, Malaysia remittance, Indonesia SNAP)	undeclared	-	-	-
Consumer Lending Licensing (UK, US, Canada credit licence registers)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

WeLab Bank Open API

WeLab Bank's Open API programme, published under the Hong Kong Monetary Authority Open API Framework and linked as "Open API" from the welab.bank site footer. The developer port...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Welab Authentication

mutualTLS · 1 scheme

SECURITY

Welab Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Conformance

Conformance

Lifecycle

Lifecycle

Access & Security 4

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

RegulatoryDisclosures

RegulatoryDisclosures

SecurityTips

SecurityTips

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 5

The organization behind the API

Website

Blog

Newsroom

About

Careers

Other 1

Properties that don't map to a standard resource type

SecondaryMarketListing

SecondaryMarketListing

Source (apis.yml)

aid: welab
name: WeLab
description: 'WeLab is a Hong Kong-headquartered fintech group founded in 2013 (incorporated November 2012 as WeLend) by Simon
  Loong, Kelly Wong and Frances Kang, operating consumer lending, digital banking and payments businesses across Hong Kong,
  mainland China and Indonesia. Its brands include WeLend (Hong Kong online lending), WeLab Digital and Taoxinji (mainland
  China), WeLab Pay, Tianmian Lab, and two licensed digital banks — WeLab Bank Limited, one of Hong Kong''s virtual banks
  licensed by the Hong Kong Monetary Authority in April 2019 and launched to the public in July 2020, and Bank Saqu (formerly
  Bank Jasa Jakarta) in Indonesia. WeLab Bank is the group''s API-bearing entity: under the HKMA Open API Framework it publishes
  an "Open API" developer portal for registered third-party service providers, backed by dedicated production and sandbox
  API gateways that require a client certificate (mutual TLS) before any request is served. Investors across its funding rounds
  include Sequoia Capital, Alibaba Entrepreneurs Fund, Credit Suisse and Allianz.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Requires approval
  confidence: low
  probe_state: gated
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.welab.bank/uploads/We_Lab_Bank_logo_en_b54140e004.png
url: https://raw.githubusercontent.com/api-evangelist/welab/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-05'
modified: '2026-08-05'
tags:
- Fintech
- Digital Banking
- virtual-bank
- Open Banking
- Hong Kong
- Indonesia
- Consumer Lending
- Payments
- hkma-open-api
- Financial Services
tags_raw:
- fintech
- digital-banking
- virtual-bank
- open-banking
- hong-kong
- indonesia
- consumer-lending
- payments
- hkma-open-api
- financial-services
- Financial-Services
apis:
- name: WeLab Bank Open API
  description: 'WeLab Bank''s Open API programme, published under the Hong Kong Monetary Authority Open API Framework and
    linked as "Open API" from the welab.bank site footer. The developer portal at portal-sandbox.welab.bank carries the API
    catalogue (account information APIs including account balance, account status and account transaction) and a help centre,
    and requires registration with WeLab Bank as a third-party service provider. The API gateways themselves are dedicated
    hosts in AWS ap-east-1 (Hong Kong): api.welab.bank for production and api-sandbox.welab.bank for the sandbox. Both enforce
    mutual TLS — an anonymous request to the sandbox gateway is answered with HTTP 400 "No required SSL certificate was sent"
    — so no operation, schema or specification is reachable without a WeLab-issued client certificate.'
  humanURL: https://portal-sandbox.welab.bank/
  baseURL: https://api.welab.bank
  tags:
  - Open Banking
  - hkma-open-api
  - Account Information
  - Digital Banking
  - Hong Kong
  tags_raw:
  - open-banking
  - hkma-open-api
  - account-information
  - digital-banking
  - hong-kong
  properties:
  - type: DeveloperPortal
    url: https://portal-sandbox.welab.bank/
  - type: Authentication
    url: authentication/welab-authentication.yml
  - type: Conformance
    url: conformance/welab-conformance.yml
  x-evidence:
    checked: '2026-08-05'
    probes:
    - url: https://api-sandbox.welab.bank/
      status: 400
      note: nginx — "No required SSL certificate was sent" (mutual TLS required)
    - url: https://api.welab.bank/
      status: 0
      note: TCP connect timeout from a US network; DNS resolves to prod-opa-gw-public-nlb (AWS ap-east-1)
    - url: https://portal-sandbox.welab.bank/
      status: 403
      note: Cloudflare block page returned to every non-interactive client
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/welab-domain-security.yml
- type: Website
  url: https://www.welab.co/
- type: DeveloperPortal
  url: https://portal-sandbox.welab.bank/
- type: Support
  url: https://www.welab.bank/en/support/
- type: HelpCenter
  url: https://www.welab.bank/en/support/faq/
- type: Blog
  url: https://www.welab.bank/en/blog/
- type: Newsroom
  url: https://www.welab.bank/en/newsroom/
- type: About
  url: https://www.welab.bank/en/about/
- type: TermsOfService
  url: https://www.welab.bank/en/legal/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.welab.bank/en/legal/privacy-policy/
- type: RegulatoryDisclosures
  url: https://www.welab.bank/en/legal/regulatory-disclosures/
- type: SecurityTips
  url: https://www.welab.bank/en/legal/security-tips/
- type: Careers
  url: https://www.welab.co/en/careers/
- type: Authentication
  url: authentication/welab-authentication.yml
- type: Conformance
  url: conformance/welab-conformance.yml
- type: Lifecycle
  url: lifecycle/welab-lifecycle.yml
- type: LLMsTxt
  url: llms/welab-llms.txt
- type: SecondaryMarketListing
  url: https://www.hiive.com/securities/welab-stock
x-enrichment:
  date: '2026-08-05'
  status: minimal
  artifacts_added: 5
  pass: local-v1
x-coverage:
  state: gated
  reason: partner-login
  detail: WeLab Bank's own footer "Open API" link goes to portal-sandbox.welab.bank, a registered-third-party-service-provider
    portal that answers every non-interactive client with a Cloudflare 403, and its sandbox gateway api-sandbox.welab.bank
    refuses anonymous requests at the TLS layer with HTTP 400 "No required SSL certificate was sent" — so the account balance/status/transaction
    contract cannot be read without a WeLab-issued client certificate.
  evidence:
  - url: https://api-sandbox.welab.bank/
    status: 400
  - url: https://portal-sandbox.welab.bank/
    status: 403
  - url: https://www.welab.bank/en/legal/maintenance-schedule/
    status: 200
  checked: '2026-08-05'

WeLab API — frequently asked questions

Does WeLab have an API?

Yes. APIs.io lists 1 API from WeLab, including WeLab Bank Open API.

How do I authenticate with the WeLab API?

WeLab uses bearer-token authentication (mutualTLS · 1 scheme). The details are profiled on APIs.io as Welab Authentication.

Is the WeLab API ready for AI agents?

WeLab has a Kin Score of 19.4 out of 100 (emerging) and an Agent Readiness score of 2.5 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/welab"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/welab/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/welab/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.