|
1 | 1 | ---
|
2 | 2 | title: Using your own API keys in GitHub Models
|
3 | 3 | shortTitle: Use custom models
|
4 |
| -intro: Learn how to integrate your preferred custom models with {% data variables.product.prodname_github_models %} by using your own LLM API keys. |
| 4 | +intro: 'Learn how to integrate your preferred custom models with {% data variables.product.prodname_github_models %} by using your own LLM API keys.' |
5 | 5 | versions:
|
6 | 6 | feature: github-models
|
7 |
| -permissions: Organization owners can add custom models to {% data variables.product.prodname_github_models %} for their organization |
| 7 | +permissions: 'Organization owners can add custom models to {% data variables.product.prodname_github_models %} for their organization' |
8 | 8 | topics:
|
9 | 9 | - Enterprise
|
10 | 10 | allowTitleToDifferFromFilename: true
|
| 11 | +redirect_from: |
| 12 | + - /github-models/github-models-at-scale/set-up-custom-model-integration-models-byok |
11 | 13 | ---
|
12 | 14 |
|
13 | 15 | {% data reusables.models.byok-preview-note %}
|
| 16 | +> |
| 17 | +> Model support is currently limited to OpenAI and AzureAI. |
14 | 18 |
|
15 | 19 | You can bring your own API keys (BYOK) to {% data variables.product.prodname_github_models %}, and enable teams to use your preferred large language model (LLM) providers across tools like Prompts, Playground, and Models in Actions. For more information about {% data variables.product.prodname_github_models %}, see [AUTOTITLE](/github-models/about-github-models).
|
16 | 20 |
|
17 | 21 | To learn about billing and pricing, see [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-models).
|
18 | 22 |
|
19 |
| ->[!NOTE] Model support is currently limited to OpenAI and AzureAI. |
20 |
| -
|
21 | 23 | ## Why bring your own API keys?
|
22 | 24 |
|
23 | 25 | As an organization owner, you may have specific requirements for governance, data security, and compliance. By setting up your own API keys, you can:
|
@@ -47,10 +49,23 @@ You must first add the relevant API keys for the organization. After that, your
|
47 | 49 | {% data reusables.profile.access_org %}
|
48 | 50 | {% data reusables.profile.org_settings %}
|
49 | 51 | {% data reusables.organizations.models-development %}
|
50 |
| -1. Under "Models permissions", select **All publishers** to enable models added by API keys. |
| 52 | +1. Under "Models permissions," select **All publishers** to enable models added by API keys. |
51 | 53 | * If this option isn't available, you need to allow the use of the model in the organization. See [AUTOTITLE](/github-models/github-models-at-scale/manage-models-at-scale#controlling-model-usage-in-your-organization).
|
52 | 54 | 1. Optionally, select **Only select models** to create a custom list of enabled or disabled models. This allows you to control which models are available to your organization.
|
53 | 55 |
|
| 56 | +## Creating an enabled or disabled models list |
| 57 | + |
| 58 | +To control which models are available to your organization, create an enabled or disabled models list as follows: |
| 59 | + |
| 60 | +{% data reusables.profile.access_org %} |
| 61 | +{% data reusables.profile.org_settings %} |
| 62 | +{% data reusables.organizations.models-development %} |
| 63 | +1. Under "Models permissions," select **Only select models**, then select **Enabled list** from the dropdown to create a list of allowed models. |
| 64 | +1. Optionally, select **Disabled list** from the dropdown if you want to create a list of blocked models. |
| 65 | +1. Above the table of models, click **Add models or publishers**. |
| 66 | +1. In the "Select models and publishers to allow" dialog, select the models and publishers you want to include in your list. |
| 67 | +1. Click **Update enabled list** to save your changes. |
| 68 | + |
54 | 69 | ## Next steps
|
55 | 70 |
|
56 | 71 | Now that you've enabled your custom models in {% data variables.product.prodname_github_models %}, learn how to:
|
|
0 commit comments