Access & Credentials

Overview · Updated May 2026

Coming from another cloud?

▸DigitalOcean·API

DigitalOcean APIhigh

Uses REST API over HTTPS with Bearer token authentication via personal access tokens, not OpenStack's Keystone token-based auth.
Base URL https://api.digitalocean.com/v2, incompatible with OpenStack APIs like Nova/Neutron.
Scoped permissions tied to granular API scopes based on team roles, unlike OpenStack role/project assignments.
Rate limits: 5000/hour, 250/minute.

DigitalOcean docs ↗

▸Hetzner·Cloud API

Cloud APIhigh

Proprietary REST API over HTTPS with Bearer token auth, not OpenStack Identity API (keystone) endpoints or mechanisms.
Base URL https://api.hetzner.cloud/v1/ with resource-specific endpoints (e.g., /servers) vs OpenStack service endpoints (nova, cinder).
No multi-project handling in single auth; separate per-project tokens vs keystone scopes/projects.
Missing identity/catalog endpoints; no service discovery via API.

Hetzner docs ↗

Access & credentials

New to Quake AI? Step 4 of the Get started sequence in the Quickstart points here for the CLI, app credentials, and AI-assistant setup that matches how you plan to work.

Overview#

Quake AI provides RESTful API services that you can use to programmatically interact with your cloud project. It also makes command line tools available for management of all cloud services.

API console provides the following features and functions related to APIs and command line tools.

View available API endpoints
Generate API token credentials
Generate S3 credentials for object storage
Generate app credentials (OpenRC files) for local environment variables and authentication

Access & Credentials

Access & credentials

Overview#

Key concepts#

See also#

See Also