1. Choose the environment
Use the Public API base URL and MCP URL for the TextMine environment you are allowed to access. For the public UK multitenant deployment:2. Choose an authentication method
Use one of the supported authentication paths. For direct/private automation, store a TextMine API key outside model-visible context:3. Run read-only checks first
Before running commands that create or update TextMine data, confirm the CLI can complete low-risk checks for the configured environment:
If any check returns an unexpected organization, empty Vault list, or authentication error, stop and fix the environment or credential before running mutating commands.
4. Use the right surface
5. Keep CLI output audit-friendly
For support and audit trails, capture non-secret identifiers in CLI output:- Organization or environment label.
- Vault ID and document ID.
- Workflow ID and run ID.
- Record schema ID and record ID.
- Task ID and task event IDs.