BYOK (Bring Your Own Key)

BYOK allows connecting external API keys from leading AI providers directly to Aymo.

This feature enables custom model access, higher usage limits, and provider-level control inside the platform. BYOK is supported across Premium and Business plans.

Overview

BYOK expands Aymo by allowing the use of models from provider accounts.

When a key is added, the platform routes requests through the connected provider while keeping Aymo’s interface and workflows intact.

Key benefits include:

• Direct access to provider models
• Unlimited usage based on provider limits
• Custom configurations and model variants
• Improved cost control for teams
• Isolation between personal and workspace-level keys

BYOK enhances flexibility while maintaining a unified workspace.

Supported Providers

Aymo supports API keys from leading AI providers:

• OpenAI
• Anthropic
• Gemini
• Mistral
• Perplexity
• Grok(xAI)
• Novita AI

Additional providers may be added as new models become available.

Adding API Keys

API keys can be added from the profile menu under the API key settings section.

Steps include:

• Select provider
• Paste the API key
• Save the configuration
• Confirm connection
• Test availability in the model selector

Once connected, provider-specific models appear inside the model selector.

Using BYOK Models

BYOK models function like default Aymo models.

They support:

• Chats
• File analysis
• Code generation
• Multi-model comparison
• Thread collaboration

Model behavior depends on provider capabilities and plan limits.

Key Isolation (soon)

BYOK keys can be assigned at:

• Personal workspace level
• Shared workspace level
• Team level (Business plan)

This ensures separation between personal usage and team usage.

Keys used in shared workspaces remain private to that workspace and are not visible to individual members.

Security and Privacy

Aymo does not store or log provider responses outside the chat context.

API keys are encrypted and stored securely within the workspace configuration.

Security features include:

• Encrypted storage
• No training on user data
• Provider-controlled usage limits
• Workspace-level isolation

All provider usage follows the respective provider’s security model.

Troubleshooting

Common BYOK issues include:

• Invalid or expired API key
• Provider model disabled or unavailable
• Incorrect model name
• Usage limits reached on the provider account
• Missing permissions for workspace-level keys

Most issues can be resolved by updating the key or checking provider quotas.

Removing API Keys

Keys can be removed from the same settings page where they were added.

Removing a key disables related BYOK models for that workspace.

Chats created with these models remain accessible but cannot generate new responses.

BYOK provides flexible, high-volume, and customizable model access inside Aymo while maintaining a secure and unified workspace.