Bitaloka
Digital service provider

Digital services,
three touch points.

Reach every service through Web (Playground), API, or MCP. Fast, offline, nothing stored.

bitaloka · api
$ curl https://api.bitaloka.io/nik/3174022501700001

{
  "nik": "3174022501700001",
  "valid": true,
  "gender": "male",
  "birth_date": "1970-01-25",
  "region": {
    "province": "DKI Jakarta",
    "regency": "Jakarta Pusat",
    "district": "Tanah Abang"
  }
}
The first service

Deterministic document parsing — computed locally, with no lookups and no data retention.

NIK

KTP identity number. Extracts gender, birth date and full region (province/regency/district) from the 16 digits, with consistency checks.

STNK

Vehicle registration plates. Normalizes and validates format, region code and serial number.

NPWP

Taxpayer identification number. Validates the 15-digit format and its built-in check digit.

Three touch points

The same services, available through the Web (Playground), the API, and MCP.

Web (Playground)

A website and an interactive playground at bitaloka.io — no code, no key.

API

A clean REST API with an OpenAPI spec and an interactive reference UI. CORS on by default.

MCP

Expose parse_nik, parse_plate and validate_npwp to any MCP-capable agent.

FAQ

Does Bitaloka query a government database?

No. Every parse is computed locally from the number itself. No external service is called and no personal data is stored or logged.

Is it free to use?

Yes — the API is open by default. Optionally protect it with an API key.

What can I parse?

NIK (KTP identity numbers), STNK vehicle plates, and NPWP taxpayer numbers. A batch endpoint accepts up to 100 mixed items in a single request.

Can I run it on my own infrastructure?

Yes — the parsers are a standalone TypeScript package (@bitaloka/core), and the API is portable so you can deploy it on your own infrastructure.

Start building in under a minute

One provider. Three touch points. Structured JSON, nothing stored.