GitHub Models Billing for GitHub Paper Customers [Public Preview] (#56168)

Co-authored-by: Felicity Chapman <felicitymay@github.com>
Co-authored-by: Sunbrye Ly <56200261+sunbrye@users.noreply.github.com>
Co-authored-by: sunbrye <sunbrye@github.com>
Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

content/github-models/github-models-at-scale/index.md

@@ -6,4 +6,5 @@ versions:
 children:
   - /use-models-at-scale
   - /manage-models-at-scale
+  - /set-up-custom-model-integration-models-byok
 ---

content/github-models/github-models-at-scale/manage-models-at-scale.md

@@ -47,4 +47,6 @@ While {% data variables.product.prodname_github_models %} for organizations and
 
 {% data reusables.models.enterprise-change-models-settings %}
 
+{% data reusables.models.enable-select-models-intro %}
+
 {% data reusables.models.enable-select-models-in-org %}

content/github-models/github-models-at-scale/set-up-custom-model-integration-models-byok.md

@@ -0,0 +1,62 @@
+---
+title: Using your own API keys in GitHub Models
+shortTitle: Use custom models
+intro: Learn how to integrate your preferred custom models with {% data variables.product.prodname_github_models %} by using your own LLM API keys.
+versions:
+  feature: github-models
+permissions: Organization owners can add custom models to {% data variables.product.prodname_github_models %} for their organization
+topics:
+  - Enterprise
+allowTitleToDifferFromFilename: true
+---
+
+{% data reusables.models.byok-preview-note %}
+
+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).
+
+To learn about billing and pricing, see [AUTOTITLE](/billing/managing-billing-for-your-products/about-billing-for-github-models).
+
+>[!NOTE] Model support is currently limited to OpenAI and AzureAI.
+
+## Why bring your own API keys?
+
+As an organization owner, you may have specific requirements for governance, data security, and compliance. By setting up your own API keys, you can:
+
+* **Governance and compliance:** Choose LLM providers that comply with your organization's policies and regulatory requirements.
+* **Cost management:** Align with your existing payment methods, contracts, credits, or negotiated rates, and avoid usage overages.
+* **Visibility and control:** Manage which models your team can access, and monitor usage through your provider's existing dashboards and billing.
+* **Flexibility:** Support custom or specialized models that your organization already uses.
+
+## Setting up your API keys to add custom models
+
+> [!IMPORTANT] We highly recommend adhering to the principle of least privilege by assigning only the minimum necessary scopes to your API keys.
+
+You must first add the relevant API keys for the organization. After that, your can specify or enable the custom models you wish to make available to users.
+
+### Adding API keys
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.custom-models %}
+1. Click **Add custom key**.
+1. In the "Add a custom key" dialog, provide details about your key. **Name** and **Key** are compulsory fields.
+1. Click **Save**.
+
+## Enabling custom models
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.models-development %}
+1. Under "Models permissions", select **All publishers** to enable models added by custom keys.
+   * 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).
+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.  
+
+## Next steps
+
+Now that you've enabled your custom models in {% data variables.product.prodname_github_models %}, learn how to:
+
+* Experiment with your custom model in the playground. See [Experimenting with AI models in the playground](/github-models/use-github-models/prototyping-with-ai-models#experimenting-with-ai-models-in-the-playground).
+
+* Store prompts on {% data variables.product.github %} so that you can iterate to fine-tune your prompts, and share them with stakeholders. See [AUTOTITLE](/github-models/use-github-models/storing-prompts-in-github-repositories).
+
+* Launch your AI application. See [Going to production](/github-models/use-github-models/prototyping-with-ai-models#going-to-production)

content/github-models/github-models-at-scale/use-models-at-scale.md

@@ -20,12 +20,13 @@ allowTitleToDifferFromFilename: true
 
 * **Centralized model management:** Control which AI models and providers are available to developers across your organization.
 * **AI development at speed:** Quickly prototype, evaluate, and optimize prompts and models.
+* **API access:** Use the {% data variables.product.prodname_github_models %} REST API to automate and integrate with enterprise workflows.
+* **Custom model integration:** Bring your own LLM API keys to connect external or custom models, giving your organization greater flexibility and control over which models are available in {% data variables.product.prodname_github_models %}, whilst keeping aligned with your existing payment methods, credits, and providers.
 * **Governance and compliance controls:** Enforce your organization's standards and monitor model usage.
 * **Cost optimization:** Avoid unexpected costs from high-priced models.
 * **Collaboration:** Share prompts and results using standard {% data variables.product.github %} development practices.
 * **Security-focused architecture:** Rest assured that your data remains within {% data variables.product.github %} and Azure and is not shared with model providers.
 * **Visual interface:** Allow non-technical team members to contribute alongside developers.
-* **API access:** Use the {% data variables.product.prodname_github_models %} REST API to automate and integrate with enterprise workflows.
 * **Version control:** All prompt and model changes go through a standard {% data variables.product.github %} commit and pull request flow so you know when and why a prompt changed.
 
 See [AUTOTITLE](/github-models/about-github-models).