ASI Cloud

Create a new VM from a template (list_vm_templates). This starts billing for the VM: confirm the name, template, size and region with the user first. Needs a payment method and stays within the account's VM limit. Returns an operation_id: poll get_operation_status until it completes, then find the VM in list_vms. For a Linux VM, pass ssh_key_id (upload_ssh_key first) so it can be reached over SSH; password login is then off.

deploy_vm

Permanently delete every object in a bucket, then the bucket. Cannot be undone: show the user the bucket name and get their explicit confirmation first. confirm_name must equal the full bucket name. One call empties for about 30 seconds; if the result says empty_incomplete, call again to carry on.

empty_and_delete_s3_bucket

Whether AI Inference is on, whether it can be turned on (and why not), the base URLs for OpenAI- and Anthropic-compatible clients, rate limits, and the models with prices (NZD per million tokens, excluding GST).

get_ai_inference_status

Live power state and IP addresses of a VM, read from the hypervisor now.

get_vm_state

Totals of the latest daily billing run, by resource type. For a month figure, note a month has many daily runs: this is the latest one, not the invoice.

get_billing_summary

Progress of an asynchronous VM operation (deploy, delete, power, rename, resize, snapshot) by the operation_id it returned. A not-found result after it ran means it finished and the record expired.

get_operation_status

AI Inference API keys (name, prefix, status, expiry, last used, updated hourly). Secrets are never listed.

list_ai_inference_keys

S3 buckets with their access key id, permissions, IP allowlist and endpoint (path-style addressing). Secret keys are never listed.

list_s3_buckets

SSH keys on the account (name, type, fingerprint, public key). Pass a key id as ssh_key_id when deploying a Linux VM.

list_ssh_keys

Snapshots of a VM (at most 3 per VM), with their snapshot ids.

list_vm_snapshots

Templates a VM can be deployed from, with default specs.

list_vm_templates

The VMs that exist now, with specs, power state and this month's estimated cost (month-to-date and full-month estimate, NZD excluding GST), as on the portal's VM list. Each row's `id` is what the other VM tools take. Set include_deleted to also list VMs deleted this month, which still cost money. The summary always covers every VM billed in the month. For a past month pass month and year (and include_deleted, since its VMs may no longer exist). It is an estimate, not the invoice (see get_billing_summary).

list_vms

Billing lines (one per resource per daily run). Filter by month and year. Use the largest batch_id in a month for that month's figures.

list_billing_records

Port-forwarding rules from the region's public IP to VMs, plus the region's public IP and subnet. Each rule's `connect_to` is the public address to use. An empty source_addresses means any address.

list_firewall_rules

The organisations this token can read: its own and, for a white-label parent, its direct child organisations. `id` is the numeric id other tools take as organisation_id; `organisation_id` is the customer code (for example S001).

list_organisations

The prices the organisation is billed at, per resource type: `amount` is NZD per unit per month, excluding GST (self-service customers get the standard self-service price list). To estimate a VM's month: vCPUs × the `vcpu_count` price + memory GiB × the `memory_size_gib` price + disk used in TiB × the `used_storage_tib` price (disk is billed on space used, not its size). S3 is `used_storage_tib_s3` per TiB stored. Estimates only: the invoice comes from billing records.

list_prices

Regions (deployment presets) that accept new VMs. Their ids are what region parameters take.

list_regions

Support tickets with ASI (subject, description, status, priority, category), most recently updated first. `meta.categories` lists the categories create_support_ticket accepts. Can lag by up to 5 minutes.

list_support_tickets

Open a support ticket with ASI's support team, who reply to the account's email. Show the user the subject and description and get their go-ahead first. Include what is affected (VM, bucket or region names and ids), what happened and when, and any error messages. Never include passwords, keys or other secrets. At most one new ticket a minute and 10 a day. If it fails as retryable, check list_support_tickets before trying again: the ticket may have been opened anyway.

create_support_ticket

Shut a VM down: whatever runs on it stops. Confirm with the user first. A powered-off VM is billed for storage only. Returns an operation_id: poll get_operation_status until it reports completed (or failed) before making another change to this VM, such as powering it on after a resize.

power_off_vm

Start a powered-off VM. Returns an operation_id: poll get_operation_status until it reports completed (or failed) before making another change to this VM, such as powering it on after a resize.

power_on_vm

Change a VM's name. Returns an operation_id: poll get_operation_status until it reports completed (or failed) before making another change to this VM, such as powering it on after a resize.

rename_vm

Change a powered-off VM's vCPUs, memory or disk (disk can only grow). Give the full new size: vcpus and memory_gib are always required, so pass the current values from list_vms for any you are not changing. The price changes with the size: confirm with the user first. Returns an operation_id: poll get_operation_status until it reports completed (or failed) before making another change to this VM, such as powering it on after a resize.

resize_vm

Roll a powered-off VM back to a snapshot. Everything written since the snapshot is lost: confirm with the user first. Returns an operation_id: poll get_operation_status until it reports completed (or failed) before making another change to this VM, such as powering it on after a resize.

restore_vm_snapshot

Revoke a key: anything using it stops within seconds. Cannot be undone. Confirm with the user first.

revoke_ai_inference_key

Issue a new access key for a bucket. The current key stops working at once, so anything using it breaks until updated: confirm with the user first. The result contains a secret that is shown once and cannot be retrieved again. It will appear in this conversation (and the AI provider's logs), so give it to the user straight away and suggest they keep it in a password manager or environment variable.

rotate_s3_key

Replace the public IPv4 /32s the bucket's key works from (at most 20); an empty list removes the restriction. Takes effect at once. Does not lift the New Zealand-only restriction. Fails while IP allowlists are not enabled.

set_s3_allowlist

Replace what the bucket's key may do. Takes effect at once and can stop applications that rely on a removed permission. Permission groups: read, write, delete, retention (retention and legal hold), restore. At least read or write.

set_s3_permissions

Turn off AI Inference: every API key stops working within seconds, including keys the user may be using right now. Confirm with the user first. Keys and usage are kept and it can be turned back on.

disable_ai_inference

Turn on pay-per-token AI Inference. This starts billing to the card on file for every token used: confirm with the user first. Needs a payment method; if ASI turned it off, only ASI can turn it back on.

enable_ai_inference

Add the user's own OpenSSH public key (one line: ssh-ed25519, ssh-rsa or ecdsa-sha2-nistp256/384/521), for example the contents of ~/.ssh/id_ed25519.pub. Never ask for a private key. At most 10 keys and one new key per minute.

upload_ssh_key