# Andromeda Docs > Guides and API reference for Andromeda GPU clusters: getting onto Slurm and Kubernetes, the Business and Platform APIs, and monitoring what you run. > ## Agent Instructions > Cluster API calls are made as a signed-in person with an OIDC bearer token. There are no API keys, and service-account tokens are refused (Business returns 401, Platform returns 403). > Platform takes the organization as the query parameter businessOrgId on most cluster routes, but as organizationId on /clusters/{clusterId}/ssh-access and /clusters/{clusterId}/kubeconfig. > The Business API uses snake_case. The Platform API uses camelCase, except /ssh-access and /machines, which use snake_case. > Business write requests need Idempotency-Key and Audit-Reason headers. > Storage capacity can grow but cannot shrink, including disk and PVC resizing. Each purchase adds capacity. > A cluster's storage can be Ceph, WEKA, or both, or NFS on its own. The Ceph quota, the purchased bytes, and Slurm's default 100 GiB shared-volume request are three different quantities. > Organization permissions cover every cluster the organization owns. A Kubernetes resource grant shares one cluster or namespace, possibly with someone outside the organization, and lets them read that cluster and fetch its kubeconfig. A grant does not give Slurm SSH, Slurm configuration, or organization storage inventory access. Slurm SSH requires organization membership and clusters.ssh. > The SSH login name is .. The gateway supports shells, commands, SFTP (including modern scp), and forwarding to loopback ports on the login node. Legacy scp and rsync need their programs on the login node. Remote forwarding and non-loopback destinations are refused. > Use POST /me/ssh-keys for personal key registration. POST /organizations/{orgID}/ssh-keys is a deprecated alias and requires no membership. Read the preferred shell from GET /me as user.login_shell; update it with PUT /me/login-preferences. > GET /clusters/{clusterId}/ssh-access returns 200 with ready and reason, even when access is not ready. ready: true does not mean compute nodes or Slurm accounting are ready. To confirm a key or shell change reached a cluster, require observation_current: true and compare ssh_key_set_generation with generation from GET /me/ssh-keys, and shell with user.login_shell from GET /me. > Adding or removing a login account restarts the cluster's login nodes, Slurm controller, and accounting service, then its compute nodes one at a time; jobs running on a restarting node end. An account is added or removed when a person with an active key gains or loses SSH access, or a person with SSH access registers their first key or revokes their last. Other key changes and shell changes restart no nodes. - [Andromeda Docs](https://docs.andromeda.ai/index.md): Guides and API reference for Andromeda GPU clusters: getting onto Slurm and Kubernetes, the Business and Platform APIs, and monitoring what you run. - [Quickstart](https://docs.andromeda.ai/clusters/quickstart.md): Sign in, find your cluster, register an SSH key, and run nvidia-smi on a GPU node through Slurm in about ten minutes. - [Concepts](https://docs.andromeda.ai/clusters/concepts.md): Organizations and permissions, the Business and Platform views of a cluster, the parts of a Slurm cluster, and how access changes reach it. - [Authentication](https://docs.andromeda.ai/clusters/authentication.md): Sign in with the andromeda CLI, use profiles for more than one environment, and call the APIs from your own OpenID Connect client. - [Permissions](https://docs.andromeda.ai/clusters/permissions.md): See which permission each task needs, check and grant permissions, and find your username on clusters. - [Connect over SSH](https://docs.andromeda.ai/clusters/ssh.md): Manage SSH keys and your login shell, check access, transfer files, forward local ports, and troubleshoot logins. - [Connect with kubectl](https://docs.andromeda.ai/clusters/kubernetes.md): Fetch a kubeconfig, sign in with kubelogin, and see which Kubernetes role each permission grants. - [Configure Slurm](https://docs.andromeda.ai/clusters/slurm-configuration.md): Partitions, slurm.conf additions, prolog and epilog scripts, what each change restarts, and organization defaults. - [Overview](https://docs.andromeda.ai/monitoring-alerting/overview.md): Grafana access, metric naming, and permissions. - [Dashboards](https://docs.andromeda.ai/monitoring-alerting/dashboards.md): Dashboard contents, panels, and key signals. - [Metrics Reference](https://docs.andromeda.ai/monitoring-alerting/metrics.md): Metrics available in your Grafana dashboards. - [Alerts](https://docs.andromeda.ai/monitoring-alerting/alerts.md): Alert rules, tiers, and Slack notifications. - [Troubleshooting](https://docs.andromeda.ai/monitoring-alerting/troubleshooting.md): Diagnostic queries for common problems. - [Slurm Monitoring](https://docs.andromeda.ai/monitoring-alerting/slurm.md): Monitoring Slurm jobs, nodes, and scheduling alongside Grafana dashboards. - [Remote Write](https://docs.andromeda.ai/monitoring-alerting/remote-write.md): Metrics delivery to external monitoring endpoints. - [Run the nanoGPT speedrun](https://docs.andromeda.ai/clusters/examples/nanogpt-speedrun.md): Rent an H100 SUNK cluster on Andromeda and train modded-nanogpt on one of its 8-GPU nodes as a Slurm batch job, in a CUDA 13 container started through Pyxis. - [Serve GLM-5.3-Flash with SGLang](https://docs.andromeda.ai/clusters/examples/glm-5.3-flash-sglang.md): Serve the 320B-parameter GLM-5.3-Flash on one 8-GPU H100 node of an Andromeda SUNK cluster with SGLang, as a Slurm batch job, and call its OpenAI-compatible API from the login node. - [API reference](https://docs.andromeda.ai/api-reference/overview.md): Base URLs, CLI usage, identifiers, organization parameters, field casing, pagination, and retrying writes for the Business and Platform APIs. - [Errors](https://docs.andromeda.ai/api-reference/errors.md): The error body, every error code the cluster endpoints return, and how to handle each. - [Identity](https://docs.andromeda.ai/api-reference/business/identity.md): Read the signed-in user, their organization memberships, an organization's details, and its members. - [Permissions](https://docs.andromeda.ai/api-reference/business/permissions.md): Read organization permissions and personal cluster grants, check cluster access, and replace member permissions. - [SSH keys](https://docs.andromeda.ai/api-reference/business/ssh-keys.md): Register, list, and revoke your Ed25519 SSH keys, and choose your login shell. - [Clusters (Business)](https://docs.andromeda.ai/api-reference/business/clusters.md): The commercial record of your organization's clusters, and who has SSH access to each. - [Clusters (Platform)](https://docs.andromeda.ai/api-reference/platform/clusters.md): Cluster state, scheduler and storage readiness, and assigned machines. - [Cluster access](https://docs.andromeda.ai/api-reference/platform/access.md): SSH connection details and kubeconfigs for a cluster. - [Slurm configuration](https://docs.andromeda.ai/api-reference/platform/scheduler.md): Read and replace a cluster's Slurm configuration and the organization default. - [Storage](https://docs.andromeda.ai/api-reference/platform/storage.md): Read the storage backends and capacity of your organization's clusters, and how to add capacity. - [Support](https://docs.andromeda.ai/support.md): How to reach Andromeda and what to send us so we can help you fast. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.