Qdrant collection lifecycle, configuration, alias, payload-index, named-vector, and optimization operations. Generated from Qdrant's immutable commit-pinned official OpenAPI schema. This leaf carries 14 of the suite's 73 admitted operations. Enroll a Qdrant Cloud or secured self-hosted deployment at its origin and store the API key in the api-key header. JSON request documents are sent verbatim, unsafe response integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and no vector-database record is represented as a task, note, or project Source.