ARVICA / DOCUMENTATION

Docs / Developers

Customer API quick start

Use scoped keys against the environment where they were issued.

Create a scoped key

A verified customer administrator can create API keys in Settings. READ permits inspection. COMPUTE_WRITE additionally allows supported deployment requests, renaming and SSH key management. Keys expire within 90 days.

Read resources

Send Authorization: Bearer with your key to /api/v1/gpus, /api/v1/deployments, /api/v1/volumes or /api/v1/balance. Balance responses are per contract and derived from ledger entries. The API allows 100 requests per key per 15 minutes.

Handle responses

Treat 401 as an authentication problem, 403 as insufficient permission and 429 as rate limiting. A successful deployment request means the request was recorded, not that a GPU is running. Use the authenticated reference for supported methods and payloads.

# Set the origin where your key was issued
export ARVICA_API_BASE="https://cloud.arvica.ai"
curl "$ARVICA_API_BASE/api/v1/gpus" \
  -H "Authorization: Bearer $ARVICA_API_KEY"
Open API reference