Pasar API is a curated developer directory and integration map for Southeast Asian APIs ~ searchable by you, and by your AI agent. It is not a replacement for official docs, SDKs, package managers, or compliance onboarding. It's built by Masterofnone.
The canonical source still matters. For government datasets, that source may be data.gov.my, OpenDOSM, data.gov.sg, data.go.th, data.go.id, or another official portal. For regulated APIs, it may be the provider's sandbox, SDK, onboarding guide, or production certification flow.
Pasar sits one layer above that. It helps a builder answer: what exists, who owns it, whether it is live, whether it is actually callable, what auth it needs, how hard implementation is, and where to go next.
Building in Southeast Asia, you lose hours hunting: which gateway does FPX or PromptPay? Is this government dataset still updated? What's the base URL, the auth, the price? The answers are scattered across a dozen docs sites, half of them stale or rebranded.
Pasar API is the place that says the quiet part clearly: some APIs are copy-paste-ready, some are docs-only, and some require proper onboarding before code is useful. Search a keyword, and leave with a working endpoint, a snippet, a caveat, or a jump to the real docs. And because the whole catalogue is also a public API and an MCP server, your AI agent can find and wire up Southeast Asian APIs without you ever leaving your editor ~ the way vibe coders actually build now.
Southeast Asia, every category ~ government open data (Malaysia, Thailand, Indonesia, Singapore, Philippines & Vietnam), payments, logistics, telco, banking, e-invoicing, maps, and more, growing toward design, AI, and whatever else builders reach for. Global tools that SEA builders rely on are included and clearly tagged.
Not every API should be presented the same way. Pasar entries are being moved toward explicit implementation labels so a builder can proceed with the right amount of caution.
Example: Malaysia's MyInvois e-invoicing API is not a simple GET endpoint and should not be treated like one. The official MyInvois SDK and LHDN/MyTax onboarding remain the source of truth for sandbox access, production credentials, document signing, validation, and digital certificate requirements. Pasar's job is to point that out before a developer wastes time with the wrong prompt or the wrong integration path.
A directory is only useful if it's true. Every commercial entry's docs link is fact-checked. Providers with no genuinely public API are excluded, not invented. Official sources are credited, commercial providers are linked back to their own docs, and complex integrations should carry caveats instead of fake "working" calls. Diligence is the whole point.
Pasar API is a Masterofnone project. The name says it ~ pasar (market): the shared place a builder comes to find any API capability they need. Built by a builder, for builders.