feat: ai gateway doc

.github/workflows/check.yml

@@ -0,0 +1,19 @@
+name: Check
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+jobs:
+  check:
+    name: check
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Check
+        run: |
+          npm install
+          npm run links

CONTRIBUTING.md

@@ -36,7 +36,7 @@ usually due to being misaligned with the project vision or out of scope. We will
 
 ### Open Issues
 
-If you're ready to contribute, start by looking at our open issues tagged as [`help wanted`](../../issues?q=is%3Aopen+is%3Aissue+label%3A"help+wanted") or [`good first issue`](../../issues?q=is%3Aopen+is%3Aissue+label%3A"good+first+issue").
+If you're ready to contribute, start by looking at our open issues tagged as `help wanted` or `good first issue`.
 
 You can comment on the issue to let others know you're interested in working on it or to ask questions.
 

Makefile

@@ -9,15 +9,9 @@ help:
 		| sed -e "s/^Makefile://" -e "s///" \
 		| awk 'BEGIN { FS = ":.*?## " }; { printf "\033[36m%-30s\033[0m %s\n", $$1, $$2 }'
 
-precommit: ## Install pre-commit hook
-	mkdir -p .git/hooks
-	rm -f .git/hooks/pre-commit
-	cp pre-commit .git/hooks/pre-commit
-	chmod +x .git/hooks/pre-commit
 
 dev.setup: ## Install dependencies
 	npm i mintlify@latest
-	make precommit
 
 dev.up: ## Start dev server
 	make dev.setup

api-reference/authentication.mdx

@@ -3,10 +3,6 @@ title: "Authentication"
 description: "How to authenticate to the Edgee API"
 ---
 
-import EdgeeSdk from '/snippets/edgee-sdk.mdx';
-
-<EdgeeSdk />
-
 The Edgee API uses API tokens to authenticate requests. You can view and manage your API token in the
 Edgee [Console](https://www.edgee.cloud/settings/tokens).
 
@@ -30,12 +26,12 @@ will also fail.
 <RequestExample>
 
   ```bash cURL with Bearer
-  curl 'https://api.edgee.app/v1/projects' \
+  curl 'https://api.edgee.ai/v1/projects' \
   -H 'Authorization: Bearer <token>'
   ```
 
   ```bash cURL with Basic Auth
-  curl 'https://api.edgee.app/v1/projects' \
+  curl 'https://api.edgee.ai/v1/projects' \
   -u '<token>:'
   # The colon prevents curl from asking for a password.
   ```

api-reference/caching/purge-cache.mdx

@@ -3,13 +3,6 @@ title: 'Purge Cache'
 openapi: 'POST /v1/projects/{id}/purge-cache'
 ---
 
-
-import EdgeeSdk from '/snippets/edgee-sdk.mdx';
-
-<EdgeeSdk />
-
 When you purge cache, Edgee will remove the specified cached content from all edge locations worldwide, which is useful when you need to update cached content, clear stale data after deployments, force fresh content to be served to users, or troubleshoot caching issues. 
 
 Query strings are automatically removed from the path before purging and cache is purged for all domains associated with the project across all edge locations worldwide. 
-
-For more information about how caching works in Edgee, see the [Caching Documentation](/services/performance/caching).