add Project Auth section

integrate-api.mdx

@@ -10,11 +10,11 @@ Hypermode makes it easy to incrementally add intelligence your app.
 You can find your project's API endpoint in the Hypermode Console, in your
 project's Home tab, in the format `https://<slug>.hypermode.app/<path>`.
 
-## API token
+## API key
 
 Hypermode protects your project's endpoint with an API key. In your project
 dashboard, navigate to **Settings** → **API Keys** to find and manage your API
-tokens.
+keys.
 
 From your app, you can call the API by passing the API token in the
 `Authorization` header. Here's an example using the `fetch` API in JavaScript:

mint.json

@@ -63,6 +63,7 @@
       "pages": [
         "create-project",
         "modify-project",
+        "project-auth",
         "modify-organization",
         "user-management"
       ]

project-auth.mdx

@@ -0,0 +1,48 @@
+---
+title: Project Auth
+description: "Manage auth for your project"
+---
+
+By default, Hypermode protects your project's endpoint with an API key, but you
+can also bring your own auth too.
+
+## Retrieve API key
+
+To use the Hypermode API key, navigate to **Settings** → **API Keys** in your
+project dashboard. From there, you can copy your API key to a secure location
+for your app to consume.
+
+## Rotate API key
+
+There might be times when you need to rotate your API key. This could be due to
+a security breach, accidentally leaking your API key, and so on.
+
+Before rotating your API key, navigate to **Settings** → **Auth** in your
+project dashboard. Take note of the name of the `PEM key` with `hypermode-` as
+the prefix. You will need to delete this as the final step of this process.
+
+Next, navigate to **Settings** → **API Keys**, and click the `Rotate` button.
+This will generate a new API key, and you can copy it to a secure location.
+
+At this point, both the old and new API keys are valid. This is so that you can
+update your app to use the new API key without incurring any downtime.
+
+Once you have updated your app to use the new API key, navigate back to
+**Settings** → **Auth**. You will notice that there are now two `PEM keys`, the
+one you saw earlier, and the new one, also prefixed with `hypermode-` but with
+different random characters. You can now safely delete the old one. This will
+invalidate the old API key.
+
+## Bring your own auth
+
+As you may have known, Modus has its own [authentication](/modus/authentication)
+features. So you can choose to implement your own auth, instead of using the
+Hypermode API key.
+
+To do this, navigate to **Settings** → **Auth** in your project dashboard. From
+there, you can upload your own verification key either as a JWKS endpoint or in
+PEM encoded format. The Modus runtime will use this to verify the JWTs sent to
+your app.
+
+At this point, you can safely delete the default Hypermode `PEM key` to
+invalidate the Hypermode API key.