Well, to be a headless CMS, you have to provide access to the content via the API.
Like you say, fetching a page whose ID you know is indeed supported out of the box.
But not being able to access the list of standalone pages via the API is definitely surprising and prohibitive in terms of a headless CMS…
@shawninder while most people are probably not using kirby fully headless if you search around you will find all kinds of plugins that help with this.
Kirby doesn’t give you everything out of the box but i think the power lies in the flexibility and ease of use to make your own. It’s more like toolkit for CMS than predefined CMS. That philosophy is everywhere. For example when you just install and look into Kirby Panel admin interface it will be empty - you have to do some work to use it. But it tends to be quick and pleasant work not some complicated mess.
Creating custom endpoint for pages will take very little time compared to the UI part for your site. But now you got superpower - you can make and use any endpoint with any data you want, wrap and cache other apis etc.