Boat

Manage machines through the API or CLI; use SSH or the command API inside a VM. Before direct API calls, credential changes, or recovery, read operations and observations, including its authentication example.

Box to Boat migration

Use boat, https://boat.dev/api/v1, /sandboxes, and BOAT_API_KEY for current examples. Docs live at https://docs.boat.dev. Existing projects may still use Box names; inspect their configuration before migrating. Renaming this skill does not authorize changing installed tools, deployed applications, or credentials. See migration notes.

Identify the account and target

1. Read project instructions and operational notes. Verify the account, organization, sandbox, and repository; reuse existing mappings instead of provisioning duplicates.
2. Load BOAT_API_KEY from the environment or the project's documented, gitignored credentials file. Do not assume a universal path, search unrelated credential stores, or print credentials. Use the secrets skill for a new key.
3. Check authentication and state with GET /me, /limits, and /sandboxes, or CLI boat status, boat list, and relevant --help. Filter output to needed fields.
4. Check installed tools. API calls need no Boat CLI or SDK. If installation is needed, read official instructions; never execute a remote installer blindly.

Use DeepAPI to check current Boat docs for uncertain behavior or fields. Check prices, limits, model catalogs, and installation commands live. Documentation does not prove an authenticated operation succeeded.

Local CLI