SDKs & Terraform overview

American Cloud ships official, typed SDKs for the three languages most infrastructure code is written in, plus an official Terraform provider for declarative infrastructure as code. All of them derive from the same OpenAPI document that drives the platform API, so they cover the public surface — virtual machines, networking, storage, Kubernetes, DNS, and more — with the same shapes the API actually speaks.

Each language page covers installation, authentication, and working first calls. For the complete operation-by-operation reference, use the API documentation — every endpoint there maps directly to an SDK method.

Authentication

All three SDKs and the Terraform provider authenticate the same way: an API token, sent in the Authorization: Bearer header. Create and manage tokens at console.americancloud.com/api-tokens. See API tokens for the steps.

• Each client reads the token from the AMERICANCLOUD_API_TOKEN environment variable, or you pass it to the client at construction.
• The token is shown once at creation — store it securely (an environment variable or secrets manager, never your repo). If it's lost, revoke the token and create a new one.
• A token has the permissions you choose at creation: Read-only to list and price resources, Full access to create, change and delete them, or Custom to pick services one by one. Start integrations with a Read-only token and create a Full access token when you're ready to create resources.
• A legacy API key (client ID and secret) still works with the API. SDK 1.8.0 and later take only a token; stay on 1.7.x if you must keep a legacy key, or replace it with a token in the console.

Versioning: the SDK version is the API version

The SDKs are versioned in lockstep with the platform API: SDK 1.8.0 is generated from API 1.8.0. The version you pin tells you exactly which API contract you're coding against — there's no separate compatibility matrix to consult. Pin exact versions and upgrade deliberately, and read each SDK's changelog before you upgrade. From 1.8.0, the SDKs authenticate with an API token.

Supply-chain posture

The npm and PyPI packages are published via Trusted Publishing (OIDC) — no long-lived tokens — and npm releases carry provenance attestations, cryptographic proof the package was built from the public repository. The Go module is consumed straight from the public GitHub repo via the Go module proxy. Source for all three lives under github.com/American-Cloud.

SDK, Terraform, or MCP?

Three ways in, by how you work:

• SDKs — you're writing software (services, CI jobs, internal tooling) that manages American Cloud resources imperatively.
• Terraform — you want infrastructure declared in versioned files, with plan and apply as the change-control loop. The provider is built on the Go SDK, so it inherits the same contract.
• MCP server — you want an AI assistant to manage infrastructure conversationally (itself built on the TypeScript SDK); the Deploy with AI recipes show what it can do.

Next steps

• TypeScript quickstart
• Go quickstart
• Python quickstart
• Terraform quickstart
• API reference — the full operation-by-operation documentation