Technically, it isn't wrong, if you consider Vulkan the technology rather than the service

isn't Vulkan the api?

'Vulkan' can refer to at least:

- Vulkan as a runtime service: 'the ability' for programs to do Vulkan things

- Vulkan as an API / specification: how programs interact with the service to do those things, or how the service interacts with programs

- Vulkan as a technology: how the API calls are implemented

Generally Vulkan refers to the specification much like how Linux refers to the kernel, but there is still Linux (kernel) vs Linux (syscall ABI) vs Linux (runtime service)