Mobile Legends Esports Intelligence

Hero

Turn public Mobile Legends: Bang Bang professional-esports wiki pages into attributed, normalized JSON.

Use Mobile Legends esports data from the Liquipedia Mobile Legends Wiki or enrich known tournament, tournament-stage, team, and player pages. Export consistent records for research, monitoring, data pipelines, dashboards, and AI workflows without maintaining MediaWiki parsing code.

This Actor uses Liquipedia's permitted MediaWiki API. It is not affiliated with or endorsed by Moonton, Mobile Legends: Bang Bang, Team Liquid, or Liquipedia.

Key Features

• Search canonical Mobile Legends: Bang Bang (MLBB) esports wiki pages.
• Normalize tournament, tournament-stage, team, and player entities.
• Extract source-backed tournament overviews, prize pools, participants, placements, match structures, team rosters, and player results when available.
• Return completeness signals, parser warnings, retrieval timestamps, and cache provenance.
• Preserve Liquipedia page attribution and CC BY-SA 3.0 license fields on every dataset record.
• Choose lightweight search, known-page enrichment, or search-and-enrich discovery.
• Reuse durable cached API responses while exposing cache status in output.
• Enforce a single request lane with minimum 2.1-second general and 31-second parse intervals.

Draft picks or bans appear only when source structure proves their meaning. Current v1 omits unproven ban data instead of relabeling veto markup.

How It Works

1. Choose search, pages, or discover mode.
2. Provide search queries or canonical Liquipedia page titles.
3. For entity modes, choose sections such as overview, prize pool, participants, matches, roster, or results.
4. The Actor validates input, queries only the Liquipedia Mobile Legends MediaWiki API, normalizes supported pages, and writes attributed records to the default dataset.
5. Read OUTPUT from the default key-value store for status, scoped errors, entity counts, request counts, cache counts, and observed policy timing.

Cold entity pages can take at least 31 seconds each because source API policy requires serialized parse requests. Warm cached runs can be faster. Missing, unsupported, invalid, or failed pages create summary errors and no entity record.

Input Example

This input is used with the exact output sample below:

{
  "mode": "search",
  "queries": ["MPL Indonesia Season 17"],
  "maxResultsPerQuery": 5,
  "maxItems": 5
}

Other supported workflows:

{
  "mode": "pages",
  "pageTitles": ["MPL/Indonesia/Season 17", "ONIC", "Kairi"],
  "sections": ["overview", "prizePool", "participants", "matches", "drafts", "roster", "results"],
  "maxItems": 3
}

{
  "mode": "discover",
  "queries": ["MSC 2026"],
  "entityTypes": ["tournament"],
  "maxCandidatesPerQuery": 5,
  "maxItems": 1,
  "sections": ["overview", "prizePool", "participants", "matches", "drafts"]
}

Unknown fields, arbitrary URLs, API bases, proxy settings, cache bypasses, rate controls, raw MediaWiki parameters, and attribution suppression are rejected.

Output Sample

Exact first dataset item from the real verification run for the input above, captured on July 25, 2026:

{
  "schemaVersion": "1.0.0",
  "recordType": "search_hit",
  "game": {
    "slug": "mobilelegends",
    "name": "Mobile Legends: Bang Bang",
    "scope": "professional_esports"
  },
  "pageId": 17579,
  "title": "MPL/Indonesia/Season 17",
  "entityTypeHint": "tournament",
  "size": 20050,
  "wordCount": 1700,
  "snippet": "Chronology Season 16 Season 18 Mobile Legends Professional League Indonesia (also known as MPL Indonesia or MPL ID) is a Professional League in Indonesia. For",
  "sourceUpdatedAt": "2026-06-24T10:21:10Z",
  "source": {
    "name": "Liquipedia Mobile Legends Wiki",
    "pageTitle": "MPL/Indonesia/Season 17",
    "pageId": 17579,
    "pageUrl": "https://liquipedia.net/mobilelegends/MPL/Indonesia/Season_17",
    "apiUrl": "https://liquipedia.net/mobilelegends/api.php",
    "retrievedAt": "2026-07-25T06:58:34.418Z",
    "cache": {
      "status": "miss",
      "storedAt": "2026-07-25T06:58:34.418Z"
    },
    "license": {
      "name": "CC BY-SA 3.0",
      "url": "https://creativecommons.org/licenses/by-sa/3.0/",
      "attribution": "Data derived from Liquipedia Mobile Legends Wiki contributors."
    }
  }
}

Exact fields vary with page type and source completeness. Entity records add classification, normalized data, completeness, warnings, and source metadata.

AI & LLM Integration

Dataset records are structured for retrieval-augmented generation (RAG), agent tools, enrichment pipelines, and prompt context. Useful patterns include:

• build an attributed MLBB esports knowledge base from entity records;
• resolve user queries to canonical pages with search_hit records before enrichment;
• generate tournament or roster briefs using normalized fields and source links;
• filter on entityType, completeness, and warnings before sending records to a model;
• retain source.pageUrl, retrievedAt, cache status, and license attribution in generated answers.

Treat model summaries as derived analysis, not source facts. Prefer entity records over search snippets for factual answers, check missing sections and warnings, and cite the included source page.

Scope and Limitations

This Actor covers public professional-esports information available on supported Liquipedia Mobile Legends pages. It does not provide:

• official Moonton data;
• player-account ranks, profiles, or account match history;
• live telemetry or live game state;
• hero abilities or heroes/meta rankings;
• guaranteed real-time statistics;
• proven draft bans where source semantics are ambiguous.

Source templates and page completeness vary. Fields can be null or empty. HTML template changes may produce warnings or require parser maintenance. Search hints are heuristic; enriched entity classification uses page categories and infobox evidence.

Source and License

Data derives from Liquipedia Mobile Legends Wiki contributors through https://liquipedia.net/mobilelegends/api.php. Source content is identified as CC BY-SA 3.0. Exports retain attribution fields.

Local Development

Requires Node.js 22+ and pnpm 10.30.0.

pnpm install --frozen-lockfile
pnpm test
pnpm test:coverage
pnpm lint
pnpm typecheck
pnpm build
pnpm format:check
apify validate-schema

Captured fixtures are test and development evidence only and are never represented as live output. Deterministic offline Actor verification:

MLBB_FIXTURE_DIR=tests/fixtures apify run --purge --input '{"mode":"pages","pageTitles":["ONIC"],"sections":["overview","roster"],"maxItems":1}'

Fixture transport activates only through local environment configuration. It is absent from public input schema and never silently replaces failed live requests.