https://customer-api.mountthor.com/compute/v2. See
Compute offerings for how this differs from
Mount Thor-managed compute.
Capabilities
Your account can use the capabilities you and Mount Thor agree on:
Anything else, such as creating a machine or a virtual machine, is not
offered. The portal doesn’t show it, the CLI refuses it, and the API answers
400 with the reason tenant_compute_customer_managed. So does a capability
your account doesn’t have. To add one, ask your Mount Thor contact.
To automate these tasks, use a service account.
Choose how to work with your Macs
- Portal
- mthr CLI
- API
See your Macs
Open the Compute page in the portal. It shows Managed by your organization, with what your account can do, and lists your Macs in the Macs card: each Mac’s serial number, hardware, location and status. The list shows 100 Macs at a time. Use Previous and Next to move between pages. To find a Mac, type its serial number, or its first characters, in Find a Mac by serial number.Click a Mac’s serial number to open its page. It shows the Mac’s serial number and, when Mount Thor knows them, its chip, model, CPU cores, memory, storage, class, site and location. Its status reads Managed by your organization because Mount Thor doesn’t track a Mac’s power or health. The page also lists the problem reports filed for that Mac.Report a problem
- Click Report a problem in the Problem reports card, or on the Mac’s page, which fills in its serial number.
- From the Compute page, enter the Mac’s Serial number.
- Describe what you see and when it started in What’s wrong, up to 4,096 bytes.
- Click Send report.
Events
If your account has events, Mount Thor can send webhook notifications about your Macs to an HTTPS endpoint you run. Ask your Mount Thor contact to enable events and for the integration details.Service accounts
A service account works through the API or the mthr CLI, as their tabs show. Every service account can readGET /compute/v2/computeprofile, which says who manages your Macs and which
capabilities your account has. For everything else, an owner binds the
service account to a custom role with the capability’s actions. See
Roles and bindings.
This role reads your Macs and files problem reports:
403
with the reason permission_denied. A role can’t add a capability your
account doesn’t have: that call still answers 400 with the reason
tenant_compute_customer_managed.