Zen

AlphaBase Zen is an optional managed provider available in deployments that enable it. It can expose curated model access through AlphaBase; availability, authentication, billing, and model policy are account- and deployment-dependent.

Note

Zen is optional. You can continue using your own providers directly.

What Zen Is For

• faster onboarding to supported model/provider combinations
• Console-based usage, billing, and entitlement visibility where enabled
• workspace-level model availability and policy controls where enabled

How To Connect

If Zen is enabled for your deployment:

1. Sign in to AlphaBase Console and create a Zen API key.
2. Run /connect in AlphaBase.
3. Select Zen and paste your key.
4. Run /models to view the models available to your account.

If Zen is not listed in the provider selector or Console, connect a supported provider directly instead; do not assume Zen access from the public docs.

Model IDs

Use Zen models in config as:

alphabase/<model-id>

Example:

{
  "agent": {
    "alpha-v3": {
      "model": "alphabase/<model-id>"
    }
  }
}

Live Catalog and Pricing

Zen model availability and pricing are dynamic and may be restricted by account or deployment. Use the console for the authoritative, current values when Zen is enabled:

• model catalog
• pricing and limits
• workspace usage
• billing settings

Avoid hard-coding static price tables in internal docs or runbooks.

Teams

Where enabled, the Console can expose workspace-level controls such as:

• member roles and access boundaries
• per-workspace usage visibility
• model availability policy at workspace level

Privacy and Data Handling

Data handling depends on the underlying model/provider selected in Zen. Review provider data policies in the console before enabling a model for production workloads.

Contact support for enterprise policy questions.