SDKs overview
Official client libraries wrap the MIOSA REST API. Every SDK does authentication, sandboxes, exec and files, snapshots, computers, agents and typed errors. Coverage varies by language; each page marks what a given SDK does not implement yet.
Languages
TypeScript
3.6.0 @miosa/sdknpm install @miosa/sdk Python
2.15.0 miosapip install miosa Go
v2.2.0 github.com/Miosa-osa/miosa-go/v2go get github.com/Miosa-osa/miosa-go/v2 Elixir
2.1.0 miosa{:miosa, "~> 2.1"} Java
0.7.0 ai.miosa:miosa-sdkimplementation 'ai.miosa:miosa-sdk:0.7.0' Rust
0.1.0 miosacargo add miosa What every SDK shares
- Auth with an API key (
msk_u_*) or an access token, read from the constructor or fromMIOSA_API_KEY. - Sandboxes with create, list, get and delete.
- Exec to run a command, and files to read and write inside a machine.
- Snapshots and computers.
- Typed errors carrying a status, a code and a request id.
Differences to expect
- Agent definitions are full CRUD in Elixir; TypeScript has definition CRUD plus separate run APIs; Python, Go and Java expose runs and settings but not definition CRUD. See each page.
- Sandbox exec in Go, Java and Elixir runs through a dedicated sandbox exec route; the handle-level convenience methods differ by language.
- File method names differ between the sandbox surface and the computer surface even inside one SDK. Each page lists the exact names.