feat(metering): Get Started guide

.github/styles/base/Dictionary.txt

@@ -423,6 +423,7 @@ Knatives
 knep
 kong
 kongair
+kong_konnect_api_request
 kong_name
 kong-ip
 Kong/kong
@@ -733,6 +734,7 @@ serializer
 serverless
 serviceaccounts
 serviceless
+service_name
 shm
 show_in_api
 Sigstore

app/_how-tos/get-started-with-metering-and-billing.md

@@ -0,0 +1,231 @@
+---
+title: Get started with Metering and Billing in {{site.konnect_short_name}}
+description: Learn how to...
+content_type: how_to
+
+permalink: /metering-and-billing/get-started/
+breadcrumbs:
+  - /metering-and-billing/
+
+products:
+    - gateway
+    - metering-and-billing
+
+works_on:
+    - konnect
+
+tags:
+    - get-started
+
+tldr: 
+  q: What is Metering and Billing in {{site.konnect_short_name}}, and how can I get started with it?
+  a: |
+    [Metering & Billing](/metering-and-billing/) provides flexible billing and metering for AI and DevTool companies. It also includes real-time insights and usage limit enforcement.
+
+    This tutorial will help you get started with Metering & Billing by setting up metering based on {{site.base_gateway}} API requests, turn raw API usage into billable product offerings by defining features and pricing plans, and start subscriptions to assign to customers.
+
+tools:
+    - deck
+
+prereqs:
+  entities:
+    services:
+        - example-service
+    routes:
+        - example-route
+  inline:
+    - title: "{{site.konnect_short_name}} roles"
+      content: |
+        You need the [? role](/konnect-platform/teams-and-roles/#service-catalog) in {{site.konnect_short_name}} to configure metering and billing.
+      icon_url: /assets/icons/kogo-white.svg
+
+cleanup:
+  inline:
+    - title: Clean up Konnect environment
+      include_content: cleanup/platform/konnect
+      icon_url: /assets/icons/gateway.svg
+
+min_version:
+    gateway: '3.4'
+next_steps:
+  - text: See all {{site.base_gateway}} tutorials
+    url: /how-to/?products=gateway
+  - text: Learn about {{site.base_gateway}} entities
+    url: /gateway/entities/
+  - text: Learn about how {{site.base_gateway}} is configured
+    url: /gateway/configuration/
+  - text: See all {{site.base_gateway}} plugins
+    url: /plugins/
+automated_tests: false
+---
+
+This getting-started guide shows how you can meter {{site.base_gateway}} API requests and invoice your customers based on their API consumption with Metering & Billing in {{site.konnect_short_name}}. 
+
+In this guide, you'll:
+* Create a Consumer that you'll map as a customer
+* Set up a meter for {{site.base_gateway}} API requests
+* Create a premium plan based on API usage
+* Start subscriptions for a customer
+* Collect an invoice for a customer on the paid premium plan and see their API usage
+
+The following diagram shows how {{site.base_gateway}} entities and Metering & Billing entities are associated:
+
+{% mermaid %}
+flowchart TB
+  subgraph gateway["<b>Kong Gateway</b>"]
+    direction LR
+        service["example-service"]
+        route["example-route"]
+        consumer1["Consumer-Kong Air"]
+  end
+  subgraph metering["<b>Konnect Metering & Billing</b>"]
+    direction LR
+        meter["Meter"]
+    subgraph plan["Premium Plan"]
+      direction LR
+          feature2["Feature (example-service)"]
+          rate-card2["Rate card"]
+    end
+    subgraph subscription["Premium Subscription"]
+      direction LR
+          customer1["Customer (Kong Air)"]
+    end
+  end
+    gateway --> metering
+    service --> meter
+    meter --> feature2
+    consumer1 --> customer1
+    subscription --> plan
+
+{% endmermaid %}
+
+
+## Create a Consumer
+
+Before you configure metering and billing, you can set up a Consumer, Kong Air. [Consumers](/gateway/entities/consumer/) let you identify the client that's interacting with {{site.base_gateway}}. Later in this guide, you'll be mapping this Consumer to a customer in Metering & Billing and assigning them to a Premium plan. Doing this allows you map existing Consumers that are already consuming your APIs to customers to make them billable.
+
+You're going to use key [authentication](/gateway/authentication/) in this tutorial, so the Consumer needs an API key to access any {{site.base_gateway}} Services.
+
+<!--vale off-->
+{% entity_examples %}
+entities:
+  consumers:
+    - username: kong-air
+      keyauth_credentials:
+        - key: air-key
+{% endentity_examples %}
+<!--vale on-->
+
+## Enable authentication
+
+Authentication lets you identify a Consumer so you can invoice them as customers after they've consumed the resource, in this case, the API request.
+This example uses the [Key Authentication](/plugins/key-auth/) plugin, but you can use any [authentication plugin](/plugins/?category=authentication) that you prefer.
+
+Enable the plugin globally, which means it applies to all {{site.base_gateway}} Services and Routes:
+
+<!--vale off-->
+{% entity_examples %}
+entities:
+  plugins:
+    - name: key-auth
+      config:
+        key_names:
+          - apikey
+{% endentity_examples %}
+<!--vale on-->
+
+## Create a meter
+
+In Metering & Billing, meters track and record the consumption of a resource or service over time. This usage can take various forms, such as API requests, compute time seconds, or tokens consumed. Usage metering is commonly event-based to ensure accuracy and auditable data.
+
+In this guide, you'll enable API Gateway requests for metering. This will meter API request traffic in Metering & Billing so that you can charge customers for API traffic usage.
+
+1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**.
+1. Enable **API Gateway Requests**.
+
+## Create a feature
+
+Meters collect raw usage data, but features make that data billable. Without a feature, usage is tracked but not invoiced. Now that you're metering API consumption, you need to associate traffic from the `example-service` Gateway Service with a feature as something you want to price or govern. 
+
+Features are customer-facing, and show up on the invoice for paid plans. Feature examples could include things like flight data requests, GPT-5 input tokens, or available LLM models. 
+
+In this guide, you'll create a feature for the `example-service` you created in the prerequisites.
+
+1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**.
+1. In the Metering & Billing sidebar, click **Product Catalog**.
+1. Click **Create Feature**.
+1. In the **Name** field, enter `example-service`.
+1. From the **Meter** dropdown menu, select "kong_konnect_api_request". 
+1. Click **Add group by filter**. 
+   The group by filter ensures you only bill for traffic to `example-service`, not all {{site.base_gateway}} traffic. This lets you offer different pricing for different APIs.
+1. From the **Group by** dropdown menu, select "service_name".
+1. From the **Operator** dropdown menu, select "Equals".
+1. From the **Value** dropdown menu, select "example-service".
+1. Click **Save**. 
+
+## Create a Premium plan
+
+Plans are the core building blocks of your product catalog. They are a collection of rate cards that define the price and access of a feature. Plans can be assigned to customers by starting a subscription.
+
+A rate card describes price and usage limits or access control for a feature or item. Rate cards are made up of the associated feature, price, and optional usage limits or access control for the feature, called entitlements.
+
+In this section, you'll create a Premium plan that grants paying customers access to the `example-service` at a rate of 5,000 requests per month:
+
+1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**.
+1. In the Metering & Billing sidebar, click **Product Catalog**.
+1. Click the **Plans** tab.
+1. Click **Create Plan**.
+1. In the **Name** field, enter `Premium`.
+1. In the **Billing cadence** dropdown menu, select "1 month".
+1. Click **Save**.
+1. Click **Add Rate Card**.
+1. From the **Feature** dropdown menu, select "example-service".
+1. Click **Next**.
+1. From the **Pricing model** dropdown menu, select "Usage Based".
+1. In the **Price per package** field, enter `1`.
+1. In the **Quantity per package** field, enter `5000`.
+1. Click **Next**. 
+1. Click **Save Rate Card**.
+1. Click **Publish Plan**.
+
+## Start a subscription
+
+Customers are the entities who pay for the consumption. In many cases, it's equal to your Consumer. Here you are going to create a customer and map our Consumer to it.
+
+1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**.
+1. In the Metering & Billing sidebar, click **Billing**.
+1. Click **Create Customer**.
+1. In the **Name** field, enter `Kong Air`.
+1. In the **Include usage from** dropdown, select "kong-air". 
+1. Click **Save**.
+1. Click the **Subscriptions** tab.
+1. Click **Create a Subscription**.
+1. From the **Subscribed Plan** dropdown, select "Premium".
+1. Click **Next**.
+1. Click **Create Subscription**.
+
+<!--Note: Want to delete a customer? Cancel their subscription first and then you can delete them.-->
+
+## Validate
+
+You can run the following command to test the that the Kong Air Consumer is invoiced correctly:
+
+<!--vale off-->
+{% validation rate-limit-check %}
+iterations: 6
+url: '/anything'
+headers:
+  - 'apikey:air-key'
+{% endvalidation %}
+<!--vale on-->
+
+This will generate six requests. Now, check the invoice that was created in Metering & Billing:
+
+1. In the {{site.konnect_short_name}} sidebar, click **Metering & Billing**.
+1. In the Metering & Billing sidebar, click **Billing**.
+1. Click the **Invoices** tab.
+1. Click **Kong Air**.
+1. Click the **Invoicing** tab.
+1. Click **Preview Invoice**.
+
+You'll see in Lines that `example-service` is listed and was used six times. In this guide, you're using the sandbox for invoices. To deploy your subscription in production, configure a payments integration in **Metering & Billing** > **Settings**.

app/_landing_pages/metering-and-billing.yaml

@@ -142,4 +142,4 @@ rows:
                 url: "https://konghq.com/contact-sales"
 
 
-
+

app/_plugins/blocks/validation.rb

@@ -18,7 +18,7 @@ def render(context) # rubocop:disable Metrics/AbcSize,Metrics/MethodLength
 
       products = @page.fetch('products', [])
 
-      unless %w[gateway kic ai-gateway operator event-gateway].any? { |p| products.include?(p) }
+      unless %w[gateway kic ai-gateway operator event-gateway metering-and-billing].any? { |p| products.include?(p) }
         raise ArgumentError,
               "Unsupported product for {% validation #{@name} %}"
       end