For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Get and manage your Solo Enterprise for agentregistry license key.

Decide which type of license to use for Solo Enterprise for agentregistry, then provide and maintain your license key.

License types

Get a license key

To get a Solo Enterprise for agentregistry license key, contact an account representative.

You can also request a trial license key instead. Note that each trial license key is typically valid for 30 days. When the license key expires, you can request a new license key by contacting your account representative.

Provide the license key during installation

To use Solo Enterprise for agentregistry, provide your license key when you install the Solo Enterprise for agentregistry Helm chart. You can either provide the key directly in your Helm values, or create a secret with the key before you install.

1. Save your license key in an environment variable.

   export AGENTREGISTRY_LICENSE_KEY=<license_key>

2. Decide how you want to provide your license key during installation.

   When you install Solo Enterprise for agentregistry, add the following settings to your helm upgrade --install command. The licensing.createSecret=true setting is required so that the chart creates the license secret from the key that you provide.

   --set licensing.createSecret=true \
   --set licensing.licenseKey=$AGENTREGISTRY_LICENSE_KEY

   After the installation completes, the chart creates a Kubernetes secret named enterprise-agentregistry-license to store your license key.

   You can specify your license key by creating a secret before you install Solo Enterprise for agentregistry.

   1. Create a secret named enterprise-agentregistry-license in the namespace that you plan to install Solo Enterprise for agentregistry in, such as agentregistry-system. The secret must contain the enterprise-agentregistry-license-key field.

      cat << EOF | kubectl apply -f -
      apiVersion: v1
      kind: Secret
      type: Opaque
      metadata:
        name: enterprise-agentregistry-license
        namespace: agentregistry-system
      stringData:
        enterprise-agentregistry-license-key: "${AGENTREGISTRY_LICENSE_KEY}"
      EOF

   2. When you install Solo Enterprise for agentregistry, the chart uses the existing secret by default (licensing.createSecret=false). The default licensing.secretName value is enterprise-agentregistry-license, which matches the secret that you created. If you used a different secret name, set licensing.secretName to that name.

3. Continue with installing Solo Enterprise for agentregistry.

Verify the license

The Solo Enterprise for agentregistry server evaluates your license key at startup and logs the result. To check the license status, review the server logs.

kubectl logs deploy/agentregistry-enterprise-server -n agentregistry-system | grep licensing

Example output for a valid license:

level=INFO msg="license status evaluated" component=licensing valid=true message="agentregistry enterprise license valid" expiration=2026-06-24T00:00:00Z

If the license is missing, invalid, or expired, the server logs a warning such as the following:

level=WARN msg="license status evaluated" component=licensing valid=false message="agentregistry enterprise license missing or invalid"

You can also confirm the license details, such as the expiration date, by copying your license key into the JWT debugger and reviewing the exp claim.

Update the license

Before your Solo Enterprise for agentregistry license expires, update the license by patching the license key secret and restarting the Solo Enterprise for agentregistry server.

1. Save the new license key in an environment variable.

   export AGENTREGISTRY_LICENSE_KEY=<new_license_key>

2. Update the enterprise-agentregistry-license secret with the new key.

   kubectl create secret generic enterprise-agentregistry-license --save-config \
     -n agentregistry-system \
     --from-literal=enterprise-agentregistry-license-key=$AGENTREGISTRY_LICENSE_KEY \
     --dry-run=client -o yaml | kubectl apply -f -

3. Restart the Solo Enterprise for agentregistry server deployment to pick up the secret change.

   kubectl rollout restart deploy/agentregistry-enterprise-server -n agentregistry-system

4. Verify that the deployment restarts and that the license is valid.

   kubectl logs deploy/agentregistry-enterprise-server -n agentregistry-system | grep licensing