← Back to Documentation
Models & Providers
Anthropic Integration
Connect Anthropic models for teams that need strong long-context and reasoning workflows.
Key Steps
- Use an organization-owned Anthropic API key and keep it in secure configuration.
- Expose approved Claude models through model aliases.
- Review latency, cost, and data policy before making Anthropic models default.
Article Scope
This guide focuses on the operational steps needed to run Orchestris with team access, provider control, and predictable usage.
Visual Reference
Provider setup
- Add the Anthropic credential to the provider catalog.
- Create aliases for the models your teams are allowed to use.
- Run a test prompt through the client before enabling broader access.
Recommended usage
- Use Anthropic models for long-form analysis, complex writing, and review workflows where they fit your policy.
- Keep lower-cost alternatives available for routine work.
- Pair access with quotas for teams that run large context prompts.
Operational review
- Watch token volume and latency after launch.
- Confirm model IDs are still current when providers release new versions.
- Update aliases instead of retraining users on provider-specific names.
Related Topics
Models & Providers
Using AI Models
Help users choose the right models without exposing provider complexity.
Models & Providers
OpenAI Integration
Connect OpenAI models and expose approved options through the provider catalog.
Models & Providers
Local Model Integration
Connect llama.cpp, OpenAI-compatible gateways, or other production-ready internal model endpoints.