[Artifacts] add guides and ArtifactFS docs

Author: elithrar

public/__redirects

@@ -40,6 +40,9 @@
 /learning-paths/ /resources/ 301
 /markdown.zip /llms-full.txt 301
 
+# artifacts
+/artifacts/api/artifactfs/ /artifacts/guides/artifact-fs/ 301
+
 # changelog
 /changelog/rss.xml /changelog/rss/index.xml 301
 /api-shield/changelog/index.xml /changelog/rss/api-shield.xml 301

src/content/changelog/artifacts/2026-04-16-artifacts-now-in-beta.mdx

@@ -1,12 +1,12 @@
 ---
-title: "Artifacts now in beta: versioned filesystem that can speak git"
-description: Artifacts is now available in beta as a versioned filesystem for Workers, APIs, and git-compatible workflows.
+title: "Artifacts now in beta: versioned filesystem with Git access"
+description: Artifacts is now available in beta as a versioned filesystem for Workers, APIs, and Git-compatible workflows.
 products:
   - artifacts
 date: 2026-04-16
 ---
 
-[Artifacts](/artifacts/) is now in beta. It provides a versioned filesystem for storing and exchanging file trees across Workers, the REST API, and git-compatible clients.
+[Artifacts](/artifacts/) is now in beta. It provides a versioned filesystem for storing and exchanging file trees across Workers, the REST API, and Git-compatible clients.
 
 Use Artifacts to publish build outputs, sync repositories, and move files between tools without inventing a new packaging format.
 
@@ -17,11 +17,10 @@ const created = await env.ARTIFACTS.create("starter-repo");
 const remote = (await created.repo.info())?.remote;
 ```
 
-You can use the REST API to create a namespace, then create a repo inside it:
+You can use the REST API to create a repo inside a namespace:
 
 ```bash
-curl "https://api.cloudflare.com/client/v4/accounts/${ARTIFACTS_ACCOUNT_ID}/artifacts/namespaces" --header "Authorization: Bearer $ARTIFACTS_JWT" --header "Content-Type: application/json" --data '{"name":"starter-namespace"}'
-curl "https://api.cloudflare.com/client/v4/accounts/${ARTIFACTS_ACCOUNT_ID}/artifacts/namespaces/starter-namespace/repos" --header "Authorization: Bearer $ARTIFACTS_JWT" --header "Content-Type: application/json" --data '{"name":"starter-repo"}'
+curl --request POST "https://artifacts.cloudflare.net/v1/api/namespaces/starter-namespace/repos" --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" --header "Content-Type: application/json" --data '{"name":"starter-repo"}'
 ```
 
 Any Git client that speaks smart HTTP can use the returned remote URL:

src/content/docs/artifacts/api/artifactfs.mdx

@@ -3,13 +3,13 @@ title: API
 description: Reference the Artifacts Workers binding, REST API, and filesystem interfaces.
 pcx_content_type: navigation
 sidebar:
-  order: 4
+  order: 5
   group:
     hideIndex: true
 ---
 
 import { DirectoryListing } from "~/components";
 
-Use the Artifacts API reference to understand the interfaces exposed across Workers, HTTP, git-compatible workflows, and filesystem access.
+Use the Artifacts API reference to understand the interfaces exposed across Workers, HTTP, and Git-compatible workflows.
 
 <DirectoryListing />

src/content/docs/artifacts/api/index.mdx

@@ -21,30 +21,22 @@ Artifacts REST routes use this base path:
 https://artifacts.cloudflare.net/v1/api/namespaces/$ARTIFACTS_NAMESPACE
 ```
 
-Some edge deployments also expose this base path:
-
-```txt
-https://artifacts.cloudflare.net/edge/v1/api/namespaces/$ARTIFACTS_NAMESPACE
-```
-
 Requests to `/v1/api/...` use Bearer authentication:
 
 ```txt
-Authorization: Bearer <GATEWAY_JWT>
+Authorization: Bearer <CLOUDFLARE_API_TOKEN>
 ```
 
-If you are calling `/edge/v1/...`, use the gateway auth required by that edge deployment.
-
 All routes below are relative to the base URL your deployment exposes. The examples use `https://artifacts.cloudflare.net/v1/api/namespaces/$ARTIFACTS_NAMESPACE`.
 
-Gateway JWTs authenticate REST control-plane routes. Repo tokens authenticate Git operations against the returned `remote` URL.
+Cloudflare API tokens authenticate REST control-plane routes. Repo tokens authenticate Git operations against the returned `remote` URL.
 
 The following examples assume:
 
 ```sh
 export ARTIFACTS_NAMESPACE="default"
 export ARTIFACTS_REPO="starter-repo"
-export ARTIFACTS_JWT="<YOUR_GATEWAY_JWT>"
+export CLOUDFLARE_API_TOKEN="<YOUR_API_TOKEN>"
 export ARTIFACTS_BASE_URL="https://artifacts.cloudflare.net/v1/api/namespaces/$ARTIFACTS_NAMESPACE"
 ```
 
@@ -173,7 +165,7 @@ export type CreateRepoResponse = ApiEnvelope<CreateRepoResult>;
 
 ```bash
 curl --request POST "$ARTIFACTS_BASE_URL/repos" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT" \
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
   --header "Content-Type: application/json" \
   --data '{
     "name": "starter-repo",
@@ -232,7 +224,7 @@ export type ListReposResponse = ApiEnvelope<RepoInfo[]>;
 
 ```bash
 curl "$ARTIFACTS_BASE_URL/repos?limit=20&sort=updated_at&direction=desc" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT"
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
 ```
 
 ```json
@@ -277,7 +269,7 @@ export type GetRepoResponse = ApiEnvelope<RemoteRepoInfo>;
 
 ```bash
 curl "$ARTIFACTS_BASE_URL/repos/$ARTIFACTS_REPO" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT"
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
 ```
 
 ```json
@@ -322,7 +314,7 @@ export type DeleteRepoResponse = ApiEnvelope<DeleteRepoResult>;
 
 ```bash
 curl --request DELETE "$ARTIFACTS_BASE_URL/repos/$ARTIFACTS_REPO" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT"
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
 ```
 
 ```json
@@ -370,7 +362,7 @@ export type ForkRepoResponse = ApiEnvelope<ForkRepoResult>;
 
 ```bash
 curl --request POST "$ARTIFACTS_BASE_URL/repos/$ARTIFACTS_REPO/fork" \
-	--header "Authorization: Bearer $ARTIFACTS_JWT" \
+	--header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
 	--header "Content-Type: application/json" \
 	--data '{
 	  "name": "starter-repo-copy",
@@ -430,7 +422,7 @@ Pass a full HTTPS Git remote URL, for example `https://github.com/facebook/react
 
 ```bash
 curl --request POST "$ARTIFACTS_BASE_URL/repos/react-mirror/import" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT" \
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
 	--header "Content-Type: application/json" \
 	--data '{
 	  "url": "https://github.com/facebook/react",
@@ -488,7 +480,7 @@ export type ListTokensResponse = ApiEnvelope<TokenInfo[]>;
 
 ```bash
 curl "$ARTIFACTS_BASE_URL/repos/$ARTIFACTS_REPO/tokens?state=all&per_page=30&page=1" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT"
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
 ```
 
 ```json
@@ -550,7 +542,7 @@ export type CreateTokenResponse = ApiEnvelope<CreateTokenResult>;
 
 ```bash
 curl --request POST "$ARTIFACTS_BASE_URL/tokens" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT" \
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
   --header "Content-Type: application/json" \
   --data '{
     "repo": "starter-repo",
@@ -593,7 +585,7 @@ export type RevokeTokenResponse = ApiEnvelope<RevokeTokenResult>;
 
 ```bash
 curl --request DELETE "$ARTIFACTS_BASE_URL/tokens/tok_123" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT"
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
 ```
 
 ```json

src/content/docs/artifacts/api/rest-api.mdx

@@ -3,7 +3,7 @@ title: Concepts
 description: Learn how Artifacts works and how to use it effectively.
 pcx_content_type: navigation
 sidebar:
-  order: 3
+  order: 4
   group:
     hideIndex: true
 ---

src/content/docs/artifacts/concepts/index.mdx

@@ -8,9 +8,7 @@ sidebar:
 
 Use this pattern when you want to discover a repo over the REST API and then hand the returned HTTPS remote to a standard Git client.
 
-This example assumes the repo already exists and that you have a gateway JWT with permission to read repo metadata and mint repo tokens.
-
-Artifacts REST auth is environment-specific in private beta. If you do not already have a gateway JWT for your Artifacts environment, use the [Workers binding](/artifacts/api/workers-binding/) instead.
+This example assumes the repo already exists and that you have a [Cloudflare API token](/fundamentals/api/get-started/create-token/) with **Artifacts** > **Edit**.
 
 ## Fetch the remote and clone the repo
 
@@ -21,16 +19,16 @@ The example below uses `jq` to extract fields from the JSON responses.
 ```bash
 export ARTIFACTS_NAMESPACE="default"
 export ARTIFACTS_REPO="starter-repo"
-export ARTIFACTS_JWT="<YOUR_GATEWAY_JWT>"
+export CLOUDFLARE_API_TOKEN="<YOUR_API_TOKEN>"
 export ARTIFACTS_BASE_URL="https://artifacts.cloudflare.net/v1/api/namespaces/$ARTIFACTS_NAMESPACE"
 
 REPO_JSON=$(curl --silent "$ARTIFACTS_BASE_URL/repos/$ARTIFACTS_REPO" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT")
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN")
 
 ARTIFACTS_REMOTE=$(printf '%s' "$REPO_JSON" | jq -r '.result.remote')
 
 TOKEN_JSON=$(curl --silent "$ARTIFACTS_BASE_URL/tokens" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT" \
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
   --header "Content-Type: application/json" \
   --data "{\"repo\":\"$ARTIFACTS_REPO\",\"scope\":\"read\",\"ttl\":3600}")
 

src/content/docs/artifacts/examples/git-client.mdx

@@ -3,7 +3,7 @@ title: Examples
 description: Explore example Artifacts integrations.
 pcx_content_type: navigation
 sidebar:
-  order: 6
+  order: 7
   group:
     hideIndex: true
 ---

src/content/docs/artifacts/examples/index.mdx

@@ -13,6 +13,6 @@ import { DirectoryListing } from "~/components";
 Start here to create, inspect, and version Artifacts from Cloudflare developer workflows.
 
 - Use **Workers** when you want the simplest path and already use Wrangler.
-- Use **REST API** only if your Artifacts environment already provides a gateway JWT in private beta.
+- Use **REST API** when you want control-plane HTTP access with a Cloudflare API token.
 
 <DirectoryListing />

src/content/docs/artifacts/get-started/index.mdx

@@ -13,21 +13,19 @@ import { LinkCard, Tabs, TabItem } from "~/components";
 
 Create an Artifacts repo with the REST API, then use a regular Git client to push and pull content.
 
-Use this guide only if your Artifacts environment already provides a gateway JWT in private beta.
-
 By the end of this guide, you will create a repo inside an existing namespace, read back the repo remote URL, push a commit, and clone the same repo with a standard Git client.
 
 ## Prerequisites
 
 You need:
 
 - A Cloudflare account with access to Artifacts.
-- A gateway JWT for the Artifacts API.
+- A [Cloudflare API token](/fundamentals/api/get-started/create-token/) with **Artifacts** > **Edit**.
 - An existing Artifacts namespace, for example `default`.
 - A local `git` client.
 - `jq`, if you want to extract response fields automatically.
 
-Artifacts REST auth is environment-specific in private beta. If you do not already have a gateway JWT for your Artifacts environment, use the [Workers get started guide](/artifacts/get-started/workers/) instead.
+For Workers-based access instead of direct HTTP calls, use the [Workers get started guide](/artifacts/get-started/workers/).
 
 ## 1. Export your environment variables
 
@@ -36,7 +34,7 @@ Set the variables used in the examples:
 ```sh
 export ARTIFACTS_NAMESPACE="default"
 export ARTIFACTS_REPO="starter-repo"
-export ARTIFACTS_JWT="<YOUR_GATEWAY_JWT>"
+export CLOUDFLARE_API_TOKEN="<YOUR_API_TOKEN>"
 export ARTIFACTS_BASE_URL="https://artifacts.cloudflare.net/v1/api/namespaces/$ARTIFACTS_NAMESPACE"
 ```
 
@@ -45,7 +43,7 @@ Use a unique repo name each time you run this guide.
 Artifacts uses Bearer authentication for control-plane requests:
 
 ```txt
-Authorization: Bearer $ARTIFACTS_JWT
+Authorization: Bearer $CLOUDFLARE_API_TOKEN
 ```
 
 ## 2. Create a repo
@@ -57,7 +55,7 @@ Choose one of the following ways to create a repo inside that namespace:
 
 ```bash
 curl --request POST "$ARTIFACTS_BASE_URL/repos" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT" \
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
   --header "Content-Type: application/json" \
   --data "{\"name\":\"$ARTIFACTS_REPO\"}"
 ```
@@ -97,7 +95,7 @@ Capture the create response once and extract the fields with `jq`:
 
 ```bash
 CREATE_RESPONSE=$(curl --silent --request POST "$ARTIFACTS_BASE_URL/repos" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT" \
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
   --header "Content-Type: application/json" \
   --data "{\"name\":\"$ARTIFACTS_REPO\"}")
 
@@ -115,7 +113,7 @@ Fetch the repo metadata when you need to recover the remote URL later:
 
 ```bash
 curl "$ARTIFACTS_BASE_URL/repos/$ARTIFACTS_REPO" \
-  --header "Authorization: Bearer $ARTIFACTS_JWT"
+  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN"
 ```
 
 ```json