Skip to main content
Model Manager is where you bring your own provider keys (BYOK) and decide which models a project can use. Everything in AgentHub that calls a model on your behalf, such as Cost Calculator executions, Agent Audit and LLM-judge evaluators, uses a model registered here. ModelHub’s chat also offers the models registered to a project. The page has three cards:
  • API Key Vault: provider keys, stored once per organization
  • Add model: register a model version against one of those keys
  • My Project Models: the models registered to the current project
Keys belong to the organization and are shared by all of its projects. Models belong to a project. Saving a key once lets every project in the organization register models against it.

​
Who can use it

Anyone in the organization can open the page. Saving or revoking keys and adding or removing models needs the manage_model_keys or manage_agents permission. With the default roles, that means Owner, Admin and Editor. Without it, actions fail with “You do not have permission to manage API keys.” (or “…to add models.” / “…to remove models.”). See Roles and permissions.

​
API Key Vault

“Keys are encrypted at rest and never shown again after saving.”

​
Save a key

1

Choose the provider

Pick from the Provider list. See Supported providers for which endpoint each one talks to.
2

Add a label (optional)

Label (optional), for example “Production OpenAI key”. Up to 200 characters. Labels are the only way to tell some keys apart later, so use one.
3

Paste the key

API key is a password field and is required. Keys longer than 8,000 characters are rejected with “That API key is too long.”
4

Click Save key

The button reads Validating… while AgentHub checks the key. On success you see “API key saved successfully.” and the key appears in the list below.
How do I get a key? next to the card description opens a step-by-step guide for creating a key with Anthropic, OpenAI or Google.

​
Validation on save

The save is rejected only when the provider’s error looks like an authentication failure (for example 401, 403, “invalid api key”). The message is “That API key didn’t work — double-check it and try again.” followed by the provider’s error in parentheses. Other errors, such as the test model being unavailable on your account, do not block the save.
The validation request is a real, billed call to your provider. It is a few tokens, so the cost is a fraction of a cent.

​
How keys are stored

  • The key is encrypted with AES-256-GCM on the server before it is written to the database. A fresh random IV is used for every key.
  • The ciphertext never leaves the server. The vault list in your browser receives only the provider, label, hint and dates.
  • After saving, the key is never shown again, anywhere. You see only a key hint: the first 4 and last 4 characters, for example sk-p…3xQz. Keys of 8 characters or fewer show as ••••••••.
  • Keys are decrypted only on the server, at the moment a model call needs them.
  • Saving and revoking a key each write an entry to your organization’s audit log (api_key.created, api_key.revoked).

​
The key list

Each active key shows the provider name, then label · hint (“Untitled” when there is no label). Self-hosted server credentials show as Self-hosted. When there are no keys, the card says “No active keys yet. Add one to enable model runs.”

​
Revoke a key

Click Revoke next to a key. The button reads Revoking…, then “API key revoked.” appears.
  • A revoked key disappears from the vault list immediately and can’t be restored. To use the provider again, save the key again as a new entry.
  • Models that were registered against it stay in My Project Models, but their key badge turns red and model calls through them fail. Remove and re-add those models against a new key.
  • There is no way to edit or rename a saved key. Revoke it and save it again.

​
Platform Demo Key

Some deployments include a Platform Demo Key, so you can try AgentHub before you bring your own key. When it is available, it appears as its own card at the top of the key list:
  • “Anthropic models · X.XXofX.XX of 50.00 left”, with a progress bar
  • Badge Platform while it has balance, Used up once it is spent
  • An info icon explaining: $50.00 of demo usage for this organization, works with any Anthropic model in the catalog, and when the balance runs out, models linked to it stop running
Rules:
  • The allowance is $50 per organization, not per user or project.
  • It works with Anthropic models only. Adding a non-Anthropic model against it fails with “The Platform Demo Key only works with Anthropic models.”
  • It can’t be revoked: “The Platform Demo Key is managed by the platform and can’t be revoked.”
  • The key value is never shown, not even as a hint.
  • Platform-funded calls draw down the same balance, including model validation when you add a model against it and Cost Calculator executions on models bound to it.
  • Once it is used up, it no longer appears in the Add model key picker. Save your own Anthropic key and add the model again against it.

​
Supported providers

The Provider list in both cards offers eleven hosted providers. Every one of them makes real calls; none is a placeholder. There is also Self-hosted / open source in the Add model card, covered below.
Keys for the eight OpenAI-compatible providers (Meta through Qwen above) are all stored under one internal provider type. The vault list shows them as Custom, and when you add, say, a Mistral model, the key picker offers every key saved for any of those eight providers. Give each key a clear label such as “Mistral prod” so you pick the right one.
Not available: Amazon (Bedrock) and Perplexity are in the pricing catalog but hidden from the lists because they have no callable models today. Azure OpenAI is not offered in Model Manager.

​
Add model

“Choose a provider then a model version.” Click Add model. The button is disabled until a key is selected and reads Validating… while AgentHub sends a real test request to that exact model with that key (8 output tokens). On success: “Model added successfully.” Errors you can see: What is stored for a model: provider, model identifier, display name, the key it is bound to, and modalities. Modalities are always text; there is no image or audio option in the form.
Model configurations also have fields for a default max output token count and a default thinking budget, but Model Manager does not expose them. Models added here leave both unset, and the Cost Calculator then uses a 1,024-token output cap per call.
You can register the same model more than once, for example once against your own key and once against the Platform Demo Key. The key badge in the list tells them apart.

​
Self-hosted and open-source models

Choose Self-hosted / open source as the provider to connect a model running on your own server. When you click Add model, AgentHub checks the server is reachable and, if it lists models, that your model name is among them (“Your server doesn’t list “name”. Available: …”). The API key and headers are encrypted in the vault like any other key, and appear there as a Self-hosted entry labelled Self-hosted · Runtime · host.
Calls to your server are made from CorePillar’s servers, not from your browser. A localhost or private-network address is only reachable if AgentHub itself runs on that network. On the hosted service, private, loopback and internal addresses are blocked, so expose the server on a public address (behind authentication) instead. Listing models times out after 8 seconds; a generation call times out after 180 seconds.

​
My Project Models

“Store a provider API key, then register at least one model to use the Playground.” Each row shows:
  • The provider icon and display name
  • A key badge: label · hint for your own keys, Platform Demo Key for the demo key, or Unknown key. The badge is red when the key is revoked, missing, or the demo balance is used up, meaning calls through this model will fail. Hover it to see “Bound to …”.
  • Provider · model identifier · modalities
To remove a model, click the trash icon, then Remove at “Remove this model?” (or Cancel). Removing a model does not revoke the key it used. There is no edit action; to change a model’s key or display name, remove it and add it again. Empty state: “Add your first model — No models registered yet — use the Add model card above to register one.” Adding and removing models writes model.created and model.deleted entries to the audit log.

​
Pricing

Every cost figure in AgentHub, from the Cost Calculator estimate to the AI Usage dashboard, comes from one built-in pricing table. Prices are in US dollars per 1,000,000 tokens, input and output separately, and were researched against each provider’s official pricing page in September 2026. Where a provider publishes a cache-hit input rate, the table carries it too. Open-weight models are priced at a representative host (Meta at Together AI). The prices are list prices. If your organization has negotiated rates, AgentHub’s dollar figures will not reflect them. A self-hosted model is priced at $0 unless you set a cost override when you add it. The table as it ships today:
The 3.6 to 3.8 Flash rates are promotional until 2027-01-01.
Off-peak rates are half; AgentHub always prices at the peak rate.
Embed v4 is an embedding model. It appears in the version list but can’t generate text, so adding it as a chat model will fail validation.
The page subtitle mentions “13 providers, 84 model versions”. The lists you can actually pick from today contain 11 providers and the 62 models above; the two hidden providers have no callable models.

Cost Calculator

Run generated scenarios against the models you registered here.

Evaluation

LLM-judge evaluators run on a model from this page.

AI Usage

See what those models cost across the organization.

Roles and permissions

Who can manage keys and models.