SDKs overview

Amika ships official SDKs that wrap the hosted API at app.amika.dev. Use them when you want to drive rigs from a program rather than the shell.

Available SDKs

@amika/sdk: rigs, agent sessions, snapshots, services, and secrets.

Read the source on GitHub.

More languages are coming. In the meantime, you can call the HTTP API directly. See API reference for the OpenAPI spec.

Use case	Tool
Day-to-day shell work, ad-hoc rig creation	CLI
Building automated pipelines, web apps, or background jobs	SDK
One-off scripts to drive an agent through a task	Either. See Programmatic usage
CI: spin up a rig per PR	SDK (or CLI in a job that has `AMIKA_API_KEY` set)

The Guides in this site show both side by side, so you can pick whichever matches the surface you’re working in.

It does not source credentials for you. The TypeScript SDK doesn’t read AMIKA_API_KEY from your environment or from disk. You pass apiKey, accessToken, or tokenSource.
It does not detect your Git repository. Pass a clone URL as repoUrl.
It does not open shells. Use the CLI’s amika rig ssh when you need one. See SSH and connect.
It does not list your hosts. Get a host’s ID for hostId from amika host get <hostname>.

The SDK can stream agent output: sendStream() reports reply text as the agent produces it. See the client reference.