# Adding a Billable Feature to Duo Agent Platform > **Updated 13 Oct 2026: date.** Public beta is no longer 19.5. Metering goes live **together with** the 90-day First Order credit grant (gitlab-org/customers-gitlab-com#19225 / gitlab-org&23973), targeted for **19.6 (19 Nov)** and no later than **19.7 (17 Dec)**. Pricing and Trust & Safety ruled out a 0-multiplier bridge (5 Oct). Please don't set a `billable_date` until the grant has a committed milestone. > > **Updated 24 Sep 2026: this request changed direction.** It was filed in August to confirm the agent stays *non-billable*. Trust & Safety has since made metering the gate for public beta, so this is now a standard request: **add `onboarding_guide/v1` to the billable list from the public-beta date.** The original text and history are in the notes below. ## Process - Please fill out this template if you are either moving an existing AI feature from Beta to GA OR adding a new AI feature in GA status. - Usage Billing requires each billable feature to be added to an opt-in list, otherwise usage of that feature will not consume credits. - Please open this request **one milestone** before you intend for the feature to be GA. - Document the decision made by the pricing team regarding the multiplier: 1. Multiplier: **Standard Duo Agent Platform credit rate (Tier 3).** No new SKU and no custom multiplier. "Free to the customer" for First Order Premium/Ultimate customers is delivered separately as a credit grant, not by keeping the agent off the billable list. 1. Person who authorized: **Jen Nguyen, Director of Pricing** (18 Sep 2026). Supersedes the August non-billable position from @sarah_zywicki, who has since left GitLab. 1. Link to decision: recorded on gitlab-com/customer-success/cx-engineering/cx-platform-engineering/agents/onboarding-agent#36 (confidential; happy to add Utilization reviewers). Trust & Safety requirement: gitlab-com/gl-security/security-operations/trust-and-safety/operations#2244. ## Details Needed 1. Feature name: **Duo Onboarding Guide** (Onboarding Agent), [AI Catalog 1003979](https://gitlab.com/explore/ai-catalog/agents/1003979/) 1. feature_qualified_name: **`onboarding_guide/v1`**. This is the Duo Chat picker path registered in gitlab-org/gitlab!245452 (`reference: 'onboarding_guide'`, `version: 'v1'`). Confirmed in billing events (Snowflake `fct_billing_events_cost`, 29 Sep). 1. feature_ai_catalog_item: **TRUE** (1003979) 1. is feature_ai_catalog_item required? **FALSE** 1. Date on which usage should consume credits: **the public-beta date, when the credit grant (#19225) is live. Target 19.6 (19 Nov 2026); latest 19.7 (17 Dec 2026).** I'll confirm the exact date on this issue at least one week ahead. ## Why this is needed - **Trust & Safety gate.** For public beta, T&S requires the picker path to be metered so it fails closed for out-of-credits namespaces and produces a Billable Events signal (operations#2244). On 24 Sep T&S confirmed this alone is enough. The Free/trial exclusion originally requested alongside it has been dropped (gitlab-org/gitlab#628148). - **Continuity.** With the CustomersDot fail-closed change for unrecognised flow types (gitlab-org&23415), an unlisted foundational agent would stop working rather than stay free. ## Open questions for Utilization 1. ~~**Who can own this?**~~ Assigned to @tvellishetty (Billing Engine), milestone 19.6. 1. ~~**Attribution.**~~ Confirmed: picker sessions emit `feature_qualified_name = 'onboarding_guide/v1'` per account. 1. **The credit grant.** Pricing's condition is that customers can see their remaining grant balance before billing starts. The grant is being built by Entitlements and Billing Engine (#19225 / gitlab-org&23973). This entry should go live with it. ## Next Steps: 1. The issue will be worked on by the Utilization Group. The Utilization Group is responsible for validating that the feature works as expected after usage billing is applied. 1. It is your responsibility to add your feature to the [DAP Billable Features table in our Docs](https://docs.gitlab.com/user/duo_agent_platform/#generally-available-features). You also need to remove the feature from the [DAP Beta Features table](https://docs.gitlab.com/user/duo_agent_platform/#beta-and-experiment-features) if it appears there. You only need to make these updates for the Docs version in which your feature will be GA. *(Owner: @nfrye, alongside the pricing-page listing in gitlab-com/marketing/digital-experience/about-gitlab-com#2065.)* ## Context - Registration: gitlab-org/gitlab!245452 (merged 20 Aug) · ai-assist!6204 (merged) - Feature flag rollout: gitlab-org/gitlab#612244 (`onboarding_guide_agent`, per top-level group; closed beta live for 15 customer groups since 22–27 Sep) - Engineering record for the T&S requirements: gitlab-org/gitlab#628148 For visibility: @brothwell1 @snachnolkar @aish.sub @vij cc @rkolosovskiy @acuffe