The missing index for Singapore APIs.
Singapore has excellent APIs. The problem is finding them. Government data lives across at least seven portals, each with its own auth flow, its own rate limits, and its own docs style. Commercial APIs for payments, logistics, and messaging live somewhere else entirely. Nobody indexes them together.
SingaporeAPI is that index. Every entry is hand-verified: the endpoint is real, the auth steps actually work, and the example response came from a real call. If an API needs a key, we document exactly how to get one, because "register for an AccountKey" is where most integrations stall.
And because more and more code is written by AI agents, the whole directory is agent-first. Every entry is available as plain text at /llms.txt, as JSON under /api/apis, and as MCP tools at /mcp. An agent can search the catalogue, pull an auth guide, and start integrating without a human opening a browser.
What is on the roadmap
Live status monitoring
Scheduled checks against every keyless endpoint, with per-API uptime badges and a status page.
Change and deprecation tracking
Singapore APIs churn: data.gov.sg v1 to v2, the OneMap auth migration. We will flag changes before they break your build.
Unified endpoints
One key, one call for common jobs: postal code lookup, public holidays, bus arrivals near a point.
Community submissions
A public catalogue repo where anyone can PR a new API or a correction.