SSH Keys

Quake AI concept: Key Pairs

• Vultr documents SSH Keys as an account-level resource under Account > SSH Keys, with dedicated create and list endpoints at `https://api.vultr.com/v2/ssh-keys`. In OpenStack Nova, keypairs are part of compute identity and are typically handled through the keypair API rather than a separate account settings area (Vultr SSH Keys, OpenStack keypair).
• The Vultr guide explicitly documents `POST /v2/ssh-keys` to create a key and `GET /v2/ssh-keys` to list keys, but it does not document an equivalent show, update, or delete API on the page we used. OpenStack keypairs support explicit `create`, `delete`, `list`, and `show` operations in the keypair CLI (How to Add Vultr SSH Keys, OpenStack keypair).
• Vultr docs say SSH Keys are used to install a specific SSH key on an instance during provisioning, which makes key selection a deployment-time action. OpenStack keypairs are modeled as server SSH access credentials that can be created and managed independently of instance launch, then referenced when creating servers (Vultr Bare Metal provisioning, OpenStack keypair).
• The Vultr SSH key docs only describe uploading a public key string and storing it in the account, with no documented server-side key generation workflow on the page we used. OpenStack's `keypair create` can generate a private key locally in `ssh-ed25519` format when no public key file is supplied, and it can also print the private key to the console (How to Add Vultr SSH Keys, OpenStack keypair).