Skip to main content
A dedicated Threetone product CLI is not released. There is no verified install package or set of Threetone login, deployment, or monitoring commands to use. You can use a standard HTTP client with the public API. Start with a read operation so you can verify authentication and workspace scope without changing a resource.
1

Choose a public operation

Open List conversations or List tests. Use the operation’s generated cURL example and documented parameters.
2

Supply a permitted credential

Follow API authentication. Keep your key in an appropriate local secret store or environment variable. Do not paste it into a shared script, recorded terminal, or issue report.
3

Handle the full response

Check the HTTP status, inspect the JSON body, and follow returned cursors for paginated reads. Preserve error details needed for diagnosis after removing private values.
A terminal client uses the same permissions and availability rules as other API clients. It cannot bypass the test, deployment, or conversation execution gates. Build automation around documented operations rather than guessed product commands.
No. Documentation development tools build this site; they do not manage your Threetone agents.
Do not assume a write is idempotent. Check the operation contract and read back state before repeating an ambiguous mutation.