Trial access and setup

Developer trial access is by invitation. Request access and wait for confirmation that your tenant is activated before running an SDK. Creating a local project does not create an Thoth tenant.

Get your connection details

Keep the supplied base URL unchanged: do not append /v1/enforce or derive a hostname from your tenant ID. The SDK appends the enforcement and event paths. Store your key privately and never commit it. If a detail is missing, ask your trial contact before proceeding.

Run your first agent

Follow Your first governed agent. It installs a tested SDK version, runs a harmless read, tests a refusal, and explains how to verify both decisions. Start with one language; the demo agent must be restored after its BLOCK before you repeat it in another language.

Then instrument your own agent, using a distinct agent ID and policy agreed with your administrator.

Know your trial boundaries

Your invitation is the source for the trial duration, limits, enabled features, and support contact. This developer path does not require MDM, SIEM, Slack writes, or the secret broker. Do not configure those integrations for the demo. Do not use the trial for production actions until your administrator has reviewed policy, credentials, approval handling, and failure behavior.

Optional: configure governance as code

The execute key cannot change governance settings. An administrator needs a separate organization key with read/write permissions, created through key management with MFA, and the supplied GovAPI base URL. This is a separate endpoint from the SDK's unified API base.

Use Configure trial settings as code for a reviewed Terraform or Pulumi workflow. The MCP proxy governs external tool calls; it does not configure Thoth's governance settings.

For connection or policy errors, start with Troubleshooting your first agent.