You are correct that Azure Functions is a separate service within Azure. However, Azure Functions is built on top of Azure App Service, which is a platform for hosting web applications, including web apps and functions. As a result, when you work with Azure Functions, you'll find some similarities with Azure App Service, including the APIs and commands.
The reason you see the LIST API and GET API under web apps for functions is because Azure Functions leverages the underlying infrastructure and capabilities provided by Azure App Service. Azure Functions can be thought of as a specialized type of web app that focuses on executing small, event-driven code snippets (functions) in response to triggers.
From an architectural standpoint, Azure Functions are implemented as extensions to Azure App Service, enabling them to inherit many of the features and capabilities of web apps. This integration allows Azure Functions to benefit from existing Azure App Service features like scaling, deployment slots, diagnostics, and more.
Although Azure Functions and Azure App Service are closely related, they also have some distinct functionality and features specific to each service. When working with Azure Functions, it's important to consider the specific functionality provided by the Azure Functions APIs and CLI commands, as they are tailored to the needs and characteristics of serverless function execution.
In summary, while Azure Functions is a separate service within Azure, it builds upon the foundation of Azure App Service. This integration allows you to leverage both the generic web app capabilities and the specialized serverless function execution model provided by Azure Functions.