A platform user consumes services from the KDP catalog: a developer, an application team, or anyone who needs a database, a cluster, or an AI capability to ship their work.
You pick a service from the catalog, then add it to your organization. From then on it is a normal Kubernetes API: the dashboard, kubectl or GitOps all work against it. So do agents. The API is structured, with a hosted MCP server and skills shipped by KDP. No ticket, no waiting on another team.
These pages cover enabling services, creating resources from them, the permissions that decide who may do what, ready-made compositions published as a single kind, and the AI tooling that drives all of it.