Default aliases
Give each alias a primary provider model and up to five ordered fallback routes from the catalog.
| Alias | Default use |
|---|---|
| Smart | Complex work and difficult reasoning |
| Fast | Responsive everyday tasks |
| Low cost | Background jobs and high-volume loops |
Applications call the alias. Changing its target does not require a new connection.
Catalog data
- Fields include provider, model, capability, context window, and usage pricing.
- The catalog synchronizes every six hours.
- Workspace targets are limited to models available through MCP.computer.
Pricing
Catalog pricing is comparison data. Actual usage is measured by the gateway and shown against the service allowance and any lower guardrails.
Provider access
| Access | Behavior |
|---|---|
| Managed | Ready without a separate provider account or provider key |
| Company supplied | Uses a company provider connection behind the same model aliases |
- Models shows each provider’s effective status and supported API interfaces.
- Changing provider access does not change the stable alias used by applications.
- Company provider credentials are handled separately from workspace configuration and are never displayed after submission.
- Company-supplied credentials become available only after they can be verified, rotated, revoked, and recovered safely.
API connections
A connection gets a one-time key for the direct gateway at gateway.mcp.computer/v1. Create and manage keys in Connections; review spend and guardrails in Reports.
- Revoking one connection does not interrupt the others.
- New connections can use every enabled company alias by default.
- Advanced settings can limit a connection to an exact alias subset.
- Company, department, person, and connection limits can all apply.
- Environment, person, and optional workflow attribution can be added in Advanced.
- Model API keys receive no MCP servers; tool connections remain separately authorized.
- Prompts and responses go directly through the gateway, not through the website.
Alias configuration
| Setting | Purpose |
|---|---|
| Display name | Human-readable label shown in the workspace |
| API name | Stable name used by applications |
| Primary route | First provider model used for a request |
| Fallback routes | Ordered provider models used when an earlier route is unavailable |
| Workspace availability | Whether the alias can be assigned to connections |
| Connection availability | All aliases or a selected subset for each key |
Smart, Fast, Low cost, and custom aliases use the same configuration contract.
Request-parameter defaults are not yet configurable in the dashboard.