[Vectorize] Vectorize available on Workers Free plan (#16855)

* [Vectorize] Vectorize available on Workers Free plan

* Update src/content/docs/vectorize/platform/pricing.mdx

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

Author: sejoker

src/content/changelogs/vectorize.yaml

@@ -5,19 +5,26 @@ productLink: "/vectorize/"
 productArea: Developer platform
 productAreaLink: /workers/platform/changelog/platform/
 entries:
+  - publish_date: "2024-09-16"
+    title: Vectorize is available on Workers Free plan
+    description: |-
+      Developers with a Workers Free plan can:
+      * Query up to 30 million queried vector dimensions / month per account.
+      * Store up to 5 million stored vector dimensions per account.
+
   - publish_date: "2024-08-14"
     title: Vectorize v1 is deprecated
     description: |
       With the new Vectorize storage engine, which supports substantially larger indexes (up to 5 million vector dimensions) and reduced query latencies, we are deprecating the original "legacy" (v1) storage subsystem.
-      
+
       To continue interacting with legacy (v1) indexes in [wrangler versions after `3.71.0`](https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.71.0), pass the `--deprecated-v1` flag.
-      
+
       For example: 'wrangler vectorize --deprecated-v1' flag to `create`, `get`, `list`, `delete` and `insert` vectors into legacy Vectorize v1 indexes. There is no currently no ability to migrate existing indexes from v1 to v2. Existing Workers querying or clients to use the REST API against legacy Vectorize indexes will continue to function.
   - publish_date: "2024-08-14"
     title: Vectorize v2 in public beta
     description: |-
       Vectorize now has a new underlying storage subsystem (Vectorize v2) that supports significantly larger indexes, improved query latency, and changes to metadata filtering.
-      
+
       Specifically:
       - Indexes can now support up to 5 million vector dimensions each, up from 200,000 per index.
       - Metadata filtering now requires explicitly defining the metadata properties that will be filtered on.

src/content/docs/vectorize/get-started/intro.mdx

@@ -19,9 +19,9 @@ This guide will instruct you through:
 
 ## Prerequisites
 
-:::note[Workers Paid plan required]
+:::note[Workers Free or Paid plans required]
 
-Vectorize is available to all users on the [Workers Paid plan](/workers/platform/pricing/#workers).
+Vectorize is available to all users on the [Workers Free or Paid plans](/workers/platform/pricing/#workers).
 
 :::
 

src/content/docs/vectorize/platform/pricing.mdx

@@ -3,23 +3,20 @@ pcx_content_type: concept
 title: Pricing
 sidebar:
   order: 1
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 :::note
 
-
-Vectorize is currently in public beta and is free to use on [Workers Paid plans](/workers/platform/pricing/#workers).
-
+Vectorize is currently in public beta and is free to use on [Workers Free or Paid plans](/workers/platform/pricing/#workers).
 
 :::
 
 Vectorize bills based on:
 
-* **Queried Vector Dimensions**: The total number of vector dimensions queried. If you have 10,000 vectors with 384-dimensions in an index, and make 100 queries against that index, your total queried vector dimensions would sum to (`(10000 + 100) * 384`) 3.878 million.
-* **Stored Vector Dimensions**: The total number of vector dimensions stored. If you have 1,000 vectors with 1536-dimensions in an index, your stored vector dimensions sum to 1.56 million.
+- **Queried Vector Dimensions**: The total number of vector dimensions queried. If you have 10,000 vectors with 384-dimensions in an index, and make 100 queries against that index, your total queried vector dimensions would sum to (`(10000 + 100) * 384`) 3.878 million.
+- **Stored Vector Dimensions**: The total number of vector dimensions stored. If you have 1,000 vectors with 1536-dimensions in an index, your stored vector dimensions sum to 1.56 million.
 
 You are not billed for CPU, memory, "active index hours", or the number of indexes you create. If you are not issuing queries against your indexes, you are not billed for queried vector dimensions.
 
@@ -39,34 +36,36 @@ The following table defines a number of example use-cases and the estimated mont
 | Large      | 768                   | 250,000 vectors   | 500,000           | `(250000+500000)*768*(0.040/1000000)`   | $23.04 / mo                    |
 | XL         | 1536                  | 500,000 vectors   | 1,000,000         | `(500000+1000000)*1536*(0.040/1000000)` | $92.16 / mo                    |
 
-<sup>included</sup> All of this usage would fall into the Vectorize usage included in the Workers Free or Paid plan.
+<sup>included</sup> All of this usage would fall into the Vectorize usage
+included in the Workers Free or Paid plan.
 
-<sup>most</sup> Most of this usage would fall into the Vectorize usage included within the Workers Paid plan.
+<sup>most</sup> Most of this usage would fall into the Vectorize usage included
+within the Workers Paid plan.
 
 ## Frequently Asked Questions
 
 Frequently asked questions related to Vectorize pricing:
 
-* When will Vectorize start charging me?
+- When will Vectorize start charging me?
 
 We intend to enable billing for Vectorize usage in January 2024.
 
-* Will Vectorize always have a free tier?
+- Will Vectorize always have a free tier?
 
 Yes, the [Workers free tier](/workers/platform/pricing/#workers) will always include the ability to prototype and experiment with Vectorize for free.
 
-* What happens if I exceed the monthly included reads, writes and/or storage on the paid tier?
+- What happens if I exceed the monthly included reads, writes and/or storage on the paid tier?
 
 You will be billed for the additional reads, writes and storage according to [Vectorize's pricing](#billing-metrics).
 
-* Does Vectorize charge for data transfer / egress?
+- Does Vectorize charge for data transfer / egress?
 
 No.
 
-* Do queries I issue from the HTTP API or the wrangler command-line count as billable usage?
+- Do queries I issue from the HTTP API or the Wrangler command-line count as billable usage?
 
 Yes: any queries you issue against your index, including from the Workers API, HTTP API and CLI all count as usage.
 
-* Does an empty index, with no vectors, contribute to storage?
+- Does an empty index, with no vectors, contribute to storage?
 
 No. Empty indexes do not count as stored vector dimensions.

src/content/partials/workers/vectorize-pricing.mdx

@@ -1,17 +1,15 @@
 ---
 {}
-
 ---
 
-|                                 | [Workers Paid](/workers/platform/pricing/#workers) | [Workers Free](/workers/platform/pricing/#workers) <sup>1</sup> |
-| ------------------------------- | -------------------------------------------------- | -------------------------------------------------- |
-| **Total queried vector dimensions** | First 50 million queried vector dimensions / month included + $0.040 per million | 30 million queried vector dimensions / month |
-| **Total stored vector dimensions** | First 10 million stored vector dimensions + $0.040 per million | 5 million stored vector dimensions |
+|                                     | [Workers Paid](/workers/platform/pricing/#workers)                               | [Workers Free](/workers/platform/pricing/#workers) |
+| ----------------------------------- | -------------------------------------------------------------------------------- | -------------------------------------------------- |
+| **Total queried vector dimensions** | First 50 million queried vector dimensions / month included + $0.040 per million | 30 million queried vector dimensions / month       |
+| **Total stored vector dimensions**  | First 10 million stored vector dimensions + $0.040 per million                   | 5 million stored vector dimensions                 |
 
-<sup>1</sup> Vectorize will be available to developers on the Workers Free plan in the future.
 ### Calculating vector dimensions
 
 To calculate your potential usage, calculate the sum of your stored + queried vectors, multiply by the dimension size, and multiply by the unit price (divided by 1 million). The formula is defined as `(stored vectors + queried vectors) * dimensions * ($0.040 / 1000000)`
 
-* For example, inserting 10,000 vectors of 768 dimensions each, and querying those 1,000 times per day (30,000 times per month) would be calculated as `(30000 * 768) = 23,040,000` queried dimensions and `(10000 * 768) = 7,680,000` stored dimensions (within the included monthly allocation)
-* Separately, and excluding the included monthly allocation, this would be calculated as `(30,000+10,000) * 768 * ($0.040 / 1,000,000)` and sum to $1.23 per month.
+- For example, inserting 10,000 vectors of 768 dimensions each, and querying those 1,000 times per day (30,000 times per month) would be calculated as `(30000 * 768) = 23,040,000` queried dimensions and `(10000 * 768) = 7,680,000` stored dimensions (within the included monthly allocation)
+- Separately, and excluding the included monthly allocation, this would be calculated as `(30,000+10,000) * 768 * ($0.040 / 1,000,000)` and sum to $1.23 per month.