docs(cloud): document the Vercel asset discovery integration

cloud/integrations.mdx

@@ -18,7 +18,7 @@
   <Card title="Webhook" icon="webhook" href="#webhook">
 
   </Card>
   <Card title="Jira" icon="jira" href="#jira">
 
   </Card>
   <Card title="GitHub" icon="github" href="#github">
@@ -48,11 +48,14 @@
   <Card title="Cloudflare" icon="cloudflare" href="#cloudflare">
 
   </Card>
   <Card title="Fastly" icon="bolt" href="#fastly">
 
   </Card>
   <Card title="DigitalOcean" icon="digital-ocean" href="#digitalocean">
 
+  </Card>
+  <Card title="Vercel" icon="cloud" href="#vercel">
+
   </Card>
 </CardGroup>
 
@@ -188,7 +191,7 @@
   },
 
   "finished": null,
   "failed_stopped": null
 }
 ```
 
@@ -276,8 +279,8 @@
     - `medium` — Medium severity count
     - `low` — Low severity count
     - `info` — Info severity count
   - `rescan_new_vulnerabilities` — New vulns since last scan, rescans only (integer)
   - `rescan_vulns_list` — List of new vulnerabilities, **max 15 items**, rescans only (array)
     - `Name` — Vulnerability name/title
     - `Severity` — Severity level (critical, high, medium, low, info)
     - `Count` — Number of instances found
@@ -385,7 +388,7 @@
     <Accordion title="Enumeration Finished" icon="circle-check">
 
 <Info>
 **Trigger:** When asset disocvery completes successfully
 
 **Type:** `finished`
 </Info>
@@ -442,7 +445,7 @@
   - `total_assets` — Total number of assets in inventory (integer)
   - `new_assets` — Number of newly discovered assets (integer)
   - `new_assets_list` — Details of newly discovered assets (array)
     - `host` — Hostname or domain name
     - `port` — Port number
     - `ip` — List of IP addresses associated with the host (array of strings)
   </Accordion>
@@ -506,7 +509,7 @@
 
 **Type:** `new_vuln`
 
 **Note:** This event is only triggered for rescans when comparing against previous results
 </Info>
 
 ```json New Vulnerability Alert Payload
@@ -575,7 +578,7 @@
 </Tip>
 
 <Note>
 If you configured severity filters (e.g., only Critical and High), only new vulnerabilities matching those severities will trigger this event and be included in the `rescan_vulns_list`.
 </Note>
     </Accordion>
 
@@ -586,7 +589,7 @@
 
 **Type:** `new_asset`
 
 **Configuration:** Can be enabled for disocvery, scan, or both based on your alerting configuration
 </Info>
 
 ```json New Asset Alert Payload
@@ -651,7 +654,7 @@
   - `total_assets` — Total number of assets in your inventory (integer)
   - `new_assets` — **Number of NEWLY discovered assets** (integer)
   - `new_assets_list` — **List of NEWLY discovered assets only** (array)
     - `host` — Hostname or domain name
     - `port` — Port number
     - `ip` — List of IP addresses associated with the host (array of strings)
   </Accordion>
@@ -667,7 +670,7 @@
 
 ## Ticketing Integrations
 
 The integrations under Ticketing support ticketing functionality as part of scanning and include support for Jira, GitHub, GitLab, and Linear. Navigate to [Scans → Configurations → Ticketing](https://cloud.projectdiscovery.io/scans/configs?type=reporting) to configure your ticketing tools.
 
 <img
   height="300"
@@ -676,9 +679,9 @@
 
 ### Jira
 
 ProjectDiscovery provides integration support for Jira to create new tickets when vulnerabilities are found.
 
 Provide a name for the configuration, the Jira instance URL , the Account ID, the Email, and the associated API token.
 
 Details on creating an API token are available [in the Jira documentation here.](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/)
 
@@ -689,7 +692,7 @@
 Provide a name for the configuration, the Organization or username, Project name, Issue Assignee, Token, and Issue Label. The Issue Label determines when a ticket is created. (For example, if critical severity is selected, any issues with a critical severity will create a ticket.)
 
 - The severity as label option adds a template result severity to any GitHub issues created.
 - Deduplicate posts any new results as comments on existing issues instead of creating new issues for the same result.
 
 Details on setting up access in GitHub [are available here.](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens)
 
@@ -701,7 +704,7 @@
 (For example, if critical severity is selected, any issues with a critical severity will create a ticket.)
 
 - The severity as label option adds a template result severity to any GitLab issues created.
 - Deduplicate posts any new results as comments on existing issues instead of creating new issues for the same result.
 
 Refer to GitLab's documentation for details on [configuring a Project Access token.](https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html#create-a-project-access-token)
 
@@ -756,7 +759,7 @@
   Click here to open the AWS integration configuration page in the ProjectDiscovery Cloud platform
 </Card>
 
 ProjectDiscovery's AWS integration allows the platform to automatically discover and monitor cloud assets across your AWS accounts. By connecting AWS to ProjectDiscovery, security teams and DevOps engineers gain continuous visibility into EC2 instances, S3 buckets, DNS records, and other resources without manual inventory. This integration leverages ProjectDiscovery's open-source **Cloudlist** engine to enumerate assets via AWS APIs. In short, it helps ensure no cloud asset goes unnoticed, enabling proactive security monitoring and easier management of your attack surface.
 
 <img
   src="/images/aws-integration.png"
@@ -768,7 +771,7 @@
 
 | Service                                               | Description                                   |
 | :---------------------------------------------------- | :-------------------------------------------- |
 | [EC2](https://aws.amazon.com/ec2/)                    | VM instances and their public IPs             |
 | [Route53](https://aws.amazon.com/route53/)            | DNS hosted zones and records                  |
 | [S3](https://aws.amazon.com/s3/)                      | Buckets (especially those public or with DNS) |
 | [Cloudfront](https://aws.amazon.com/cloudfront/)      | CDN distributions and their domains           |
@@ -776,8 +779,8 @@
 | [EKS](https://aws.amazon.com/eks/)                    | Kubernetes cluster endpoints                  |
 | [ELB](https://aws.amazon.com/elasticloadbalancing/)   | Load balancers (Classic ELB and ALB/NLB)      |
 | [ELBv2](https://aws.amazon.com/elasticloadbalancing/) | Load balancers (Classic ELB and ALB/NLB)      |
 | [Lambda](https://aws.amazon.com/lambda/)              | Serverless function endpoints                 |
 | [Lightsail](https://aws.amazon.com/lightsail/)        | Lightsail instances (simplified VPS)          |
 | [Apigateway](https://aws.amazon.com/api-gateway/)     | API endpoints deployed via Amazon API Gateway |
 
 By covering these services, ProjectDiscovery can map out a broad range of AWS assets in your account. (Support for additional services may be added over time.)
@@ -1001,7 +1004,7 @@
 
 **Step 4: Grant the WIF Role AssumeRole Permission**
 
 Allow the WIF role to assume scanner roles. Use a wildcard to cover all accounts, or list specific account ARNs.
 
 ```bash
 cat > assume-scanner-policy.json <<EOF
@@ -1155,9 +1158,9 @@
 
 #### API Setup
 
 You can set up the AWS integration entirely through the API. The process involves creating a cloudlist configuration, verifying it, and then using it to create an enumeration.
 
 The cloudlist configuration is a YAML array that must be **base64-encoded** before sending it to the API. Each connection method uses a different YAML structure, but the API calls are the same.
 
 **Configuration Format**
 
@@ -1165,9 +1168,9 @@
   <Accordion title="Single AWS Account (Access Key & Secret)">
     ```yaml
     - provider: aws
       aws_access_key: "AKIAIOSFODNN7EXAMPLE"
       aws_secret_key: "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
       aws_session_token: "optional-session-token"
       services:
         - ec2
         - route53
@@ -1178,10 +1181,10 @@
   <Accordion title="Multiple AWS Accounts (Assume Role)">
     ```yaml
     - provider: aws
       aws_access_key: "AKIAIOSFODNN7EXAMPLE"
       aws_secret_key: "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
       assume_role_name: "ProjectDiscoveryReadOnlyRole"
       account_ids:
         - "123456789012"
         - "987654321098"
       services:
@@ -1194,9 +1197,9 @@
   <Accordion title="Cross-Account Role (Role ARN)">
     ```yaml
     - provider: aws
       assume_role_arn: "arn:aws:iam::123456789012:role/ProjectDiscoveryRole"
       external_id: "your-external-id"
       assume_role_session_name: "projectdiscovery_role"
       services:
         - ec2
         - route53
@@ -1240,7 +1243,7 @@
 
 **Step 2: Create the Integration**
 
 Once verified, send the base64-encoded configuration to create a cloudlist config:
 
 ```bash
 curl -X POST https://api.projectdiscovery.io/v1/scans/config \
@@ -1299,9 +1302,9 @@
 |:---|:---|
 | [Cloud DNS](https://cloud.google.com/dns) | DNS zones and records |
 | [Kubernetes Engine](https://cloud.google.com/kubernetes-engine) | GKE cluster endpoints |
 | [Compute Engine](https://cloud.google.com/products/compute) | VM instances and public IPs |
 | [Cloud Storage](https://cloud.google.com/storage) | Buckets |
 | [Cloud Functions](https://cloud.google.com/functions) | Serverless function endpoints |
 | [Cloud Run](https://cloud.google.com/run) | Container service URLs |
 
 #### Enumeration Scope
@@ -1641,7 +1644,7 @@
 <Note>
 `YOUR_PROJECT_NUMBER` is the numeric project number, not the project ID. Find it with:
 ```bash
 gcloud projects describe YOUR_PROJECT_ID --format='value(projectNumber)'
 ```
 </Note>
 
@@ -1855,7 +1858,7 @@
 
    - If you only need specific services, you can further reduce actions. For example:
      - Virtual machines: `Microsoft.Compute/virtualMachines/read`, plus RG/subscription reads
      - Public IPs: `Microsoft.Network/publicIPAddresses/read`
      - Traffic Manager: `Microsoft.Network/trafficManagerProfiles/read`
      - Storage Accounts: `Microsoft.Storage/storageAccounts/read`
      - AKS Clusters: `Microsoft.ContainerService/managedClusters/read`
@@ -1878,9 +1881,9 @@
 
 
 
 ### Alibaba Cloud
 
 <Card title="Configure Alibaba Cloud Integration" icon="cloud" color="#FF6A00" href="https://cloud.projectdiscovery.io/assets/configure?provider=alibaba">
   Click here to open the Alibaba Cloud integration configuration page in the ProjectDiscovery Cloud platform
 </Card>
 
@@ -1891,13 +1894,13 @@
   style={{ width:"62%" }}
 />
 
 Supported Alibaba Cloud Services:
 
 - ECS Instances
 
 **Alibaba Integration Method**
 
 This guide details the secure, best-practice method for connecting to Alibaba Cloud using a dedicated RAM user with read-only permissions.
 
 1. **Create a RAM User for API Access:**
    - Navigate to the **RAM (Resource Access Management) console**. [Ref](https://ram.console.aliyun.com/manage/ak)
@@ -1915,11 +1918,11 @@
    - Select the **System Policy** type.
    - Search for and select the `AliyunReadOnlyAccess` policy and click **OK**. This is the official, managed policy for read-only access to all cloud resources.
 4. **Find Your Region ID and Connect:**
    - Identify the **Region ID** for the resources you plan to monitor. You can find the official list in the Alibaba Cloud documentation here: [Regions and zones](https://www.alibabacloud.com/help/en/doc-detail/40654.htm) (This link lists the specific IDs required for API configuration).
    - Use the credentials you have collected to fill in the fields in ProjectDiscovery:
      - **Alibaba Region ID**: The target region, for example, `us-east-1`.
      - **Alibaba Access Key**: The AccessKey ID from Step 2.
      - **Alibaba Access Key Secret**: The AccessKey Secret from Step 2.
    - Enter a unique **Integration Name** and click **Verify**.
 
 References:
@@ -1960,8 +1963,8 @@
   - Clusters with public IP addresses
 </Note>
 
 1. **Prepare Base64-Encoded Kubeconfig**
    - Your kubeconfig file is typically located at:
 
      ```
      ~/.kube/config
@@ -1971,11 +1974,11 @@
      ```
      cat ~/.kube/config | base64
      ```
    - Paste the output into the **Kubeconfig** field in the UI.
 
      > ⚠️ Ensure the entire content is copied without extra whitespace.
 2. **Specify Context (Optional)**
    - If your kubeconfig has multiple contexts, find them with:
 
      ```
      kubectl config get-contexts
@@ -1994,7 +1997,7 @@
 
 If your Kubernetes integration fails, the most common cause is cluster accessibility:
 
 - **Internal Clusters**: Clusters only accessible within private networks (VPN, internal VPCs) cannot be reached by ProjectDiscovery
 - **Firewall Restrictions**: Ensure your cluster's API server and services are accessible from the internet
 - **Network Policies**: Check that network policies allow external access to required endpoints
 - **Load Balancer Configuration**: Verify that external load balancers are properly configured and accessible
@@ -2025,7 +2028,7 @@
 - DNS and CDN assets
 
 <Note>
   Connecting a Cloudflare integration also enables **origin IP exposure** detection under [Misconfigurations](/api-reference/enumerations/list-enumeration-misconfigurations). When a hostname from your asset inventory resolves to the same IP as the origin behind one of your proxied Cloudflare records, it is flagged as an origin exposure finding.
 </Note>
 
 **Cloudflare Integration Methods:**
@@ -2064,7 +2067,7 @@
 
 ### Fastly
 
 <Card title="Configure Fastly Integration" icon="bolt" color="#FF282D" href="https://cloud.projectdiscovery.io/assets/configure?provider=fastly">
   Click here to open the Fastly integration configuration page in the ProjectDiscovery Cloud platform
 </Card>
 
@@ -2075,16 +2078,16 @@
   style={{ width:"65%" }}
 />
 
 **Fastly Integration Method**
 
 - Go to Fastly [account settings](https://manage.fastly.com/account/personal).
 - Under **API**, click **Create API token** if you don’t already have one.
 - Copy the API Key.
 - Now enter API Key in ProjectDiscovery Cloud Platform.
 - Give a unique Integration name and click **Verify**.
 
   <Tip>
     Tip: In Fastly's documentation and interfaces, "API Key" and "API Token" refer to the same thing. You can use the terms interchangeably throughout this guide.
   </Tip>
 
 References:
@@ -2121,3 +2124,72 @@
 
 1. https://docs.digitalocean.com/reference/api/create-personal-access-token/
 2. https://docs.digitalocean.com/reference/api/
+
+### Vercel
+
+<Card title="Configure Vercel Integration" icon="cloud" href="https://cloud.projectdiscovery.io/assets/configure?provider=vercel">
+  Click here to open the Vercel integration configuration page in the ProjectDiscovery Cloud platform
+</Card>
+
+<img
+  src="/images/Vercel_integration_screen.png"
+  alt="Vercel Integration Screen"
+  title="Vercel Integration Screen"
+  style={{ width:"65%" }}
+/>
+
+ProjectDiscovery's Vercel integration pulls the hostnames Vercel serves for your projects into your asset inventory, so the frontends your team ships continuously are scanned alongside the rest of your attack surface. Like the other cloud integrations it runs on ProjectDiscovery's open-source **Cloudlist** engine, reading the Vercel REST API with a token you supply.
+
+Supported Vercel Services:
+
+| Service                                                       | Description                                                                |
+| :------------------------------------------------------------ | :------------------------------------------------------------------------- |
+| [Deployments](https://vercel.com/docs/deployments)            | Deployment hostnames from each project's latest deployments, flagged public or private |
+| [Domains](https://vercel.com/docs/domains)                    | Production domain aliases assigned to each project                         |
+
+**Create the token in Vercel**
+
+- Set the scope selector in the Vercel dashboard to your personal account rather than a team, then open the [Account Tokens page ↗](https://vercel.com/account/tokens).
+- Click **Create Token** and enter a descriptive name.
+- Open the **Scope** dropdown and choose how far the token reaches. See the table below for how each choice behaves here.
+- Choose an **Expiration** and click **Create**.
+- Copy the token now. Vercel shows the value once, prefixed `vcp_`.
+
+<Note>
+  Some Vercel teams require two-factor authentication or SAML before a token can be scoped to them. The Vercel dashboard tells you when you select such a team.
+</Note>
+
+**Choosing a scope**
+
+| Token scope                                          | What ProjectDiscovery enumerates                              | Team ID field                       |
+| :--------------------------------------------------- | :------------------------------------------------------------ | :---------------------------------- |
+| **Team** (select the team, then **All Projects**)    | Every project in that team                                     | Leave empty                         |
+| **Full Account**                                     | Your personal account's projects, unless you supply a Team ID  | Required to reach a team's projects |
+| **Project**                                          | That single project only                                       | Leave empty                         |
+
+**Connect it in ProjectDiscovery**
+
+- Enter the token as **API Access Token**.
+- Enter a **Team ID** (`team_xxx`, shown in Vercel under **Team Settings → General**) only when you are using a Full Account token and want a team's projects. Team-scoped and project-scoped tokens already carry their team, so leave the field empty for those.
+- Give a unique **Integration Name**, set a discovery **Frequency** or keep the daily default, and click **Verify**.
+
+Both services are enumerated by default. To restrict an integration to one of them, create it from [Integrations](https://cloud.projectdiscovery.io/integrations) instead, where the connection form exposes a **Services** selector, or set `services` directly in a Cloudlist configuration as shown in [Cloudlist Providers](/opensource/cloudlist/providers#vercel).
+
+<Tip>
+  A team-scoped token is the least-privilege choice for this integration. It reaches one team, needs no Team ID, and can be revoked without disturbing your other Vercel automation. Pair it with the shortest expiration your rotation schedule allows.
+</Tip>
+
+<Warning>
+  Vercel access tokens have no read-only permission setting. A token carries the permissions of the account that created it, within the scope you select, so scope and expiry are the only controls available to you. ProjectDiscovery issues read requests only.
+</Warning>
+
+**What this integration does not cover**
+
+- **Full deployment history**: only the deployments Vercel reports as a project's latest are enumerated, not every deployment ever created for that project.
+- **Preview and branch aliases**: domains are read from each project's production target, so aliases pointing at preview or branch environments are not enumerated.
+- **The shared `vercel.app` suffix**: the integration reads the projects your token can see. It does not enumerate the wider `*.vercel.app` public suffix.
+
+References:
+
+1. https://vercel.com/docs/accounts/access-tokens
+2. https://vercel.com/docs/rest-api

opensource/cloudlist/providers.mdx

@@ -1,10 +1,10 @@
 ---
 title: Cloudlist Providers
 description: "Supported cloud providers"
 sidebarTitle: Providers
 ---
 
 This guide offers insights into each supported provider, enabling you to leverage Cloudlist's capabilities to their fullest extent for comprehensive asset visibility and control.
 
 ## Major Cloud Providers
 
@@ -268,7 +268,7 @@
   subscription_id: $AZURE_SUBSCRIPTION_ID
 ```
 
 **4. Managed Identity (Azure VMs, App Services, AKS):**
 ```yaml
 - provider: azure
   id: azure-hosted
@@ -303,22 +303,22 @@
 **Authentication Priority (when using auto-detection):**
 1. Environment Variables (AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID)
 2. Workload Identity (Kubernetes service account tokens)
 3. Managed Identity (Azure VMs, App Services, AKS nodes)
 4. Azure CLI (az login session)
 
 References:
 1. https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli
 2. https://docs.microsoft.com/en-us/cli/azure/ad/sp?view=azure-cli-latest#az_ad_sp_create_for_rbac
 3. https://docs.microsoft.com/en-us/cli/azure/authenticate-azure-cli
 
 ### Alibaba Cloud
 
 Suppoted Alibaba Cloud Services:
   - ECS Instances
 
 **Example Config:**
 
 Alibaba Cloud can be integrated by using the following configuration block.
 
 ```yaml
 - provider: alibaba # provider is the name of the provider
@@ -332,7 +332,7 @@
   alibaba_access_key_secret: $ALIBABA_ACCESS_KEY_SECRET
 ```
 
 Alibaba Cloud Access Key ID and Secret can be created by visiting https://ram.console.aliyun.com/manage/ak
 
 References:
 1. https://www.alibabacloud.com/help/faq-detail/142101.htm
@@ -347,7 +347,7 @@
 
 **Example Config:**
 
 Digitalocean can be integrated by using the following configuration block.
 
 ```yaml
 - provider: do # provider is the name of the provider
@@ -357,19 +357,19 @@
   digitalocean_token: $DIGITALOCEAN_TOKEN
 ```
 
 `digitalocean_token` can be generated from the Digitalocean Control Panel. We recommend only giving Read Access to the token.
 
 References:
 1. https://www.digitalocean.com/docs/apis-clis/api/create-personal-access-token/
 
 ### SCW (Scaleway)
 
 Supported Scaleway Services:
   - Instances
 
 **Example Config:**
 
 Scaleway can be integrated by using the following configuration block.
 
 ```yaml
 - provider: scw # provider is the name of the provider
@@ -379,7 +379,7 @@
   scaleway_access_token: $SCALEWAY_ACCESS_TOKEN
 ```
 
 `scaleway_access_key` and `scaleway_access_token` can be generated from the Credentials Options in scaleway console.
 
 References - 
 1. https://www.scaleway.com/en/docs/generate-api-keys/
@@ -418,14 +418,14 @@
 References:
 1. https://devcenter.heroku.com/articles/platform-api-quickstart#authentication
 
 ### Linode
 
 Supported Linode Services:
   - Instances
 
 **Example Config:**
 
 Linode can be integrated by using the following configuration block.
 
 ```yaml
 - provider: linode # provider is the name of the provider
@@ -440,16 +440,49 @@
 References: 
 1. https://www.linode.com/docs/guides/getting-started-with-the-linode-api/#get-an-access-token
 
+### Vercel
+
+Supported Vercel Services:
+  - Deployments
+  - Domains
+
+**Example Config:**
+
+Vercel can be integrated by using the following configuration block.
+
+```yaml
+- provider: vercel # provider is the name of the provider
+  # id is the name defined by user for filtering (optional)
+  id: staging
+  # vercel_api_token is the access token for the vercel account
+  vercel_api_token: $VERCEL_API_TOKEN
+  # vercel_team_id scopes enumeration to a team, only needed with a
+  # Full Account token (optional)
+  vercel_team_id: $VERCEL_TEAM_ID
+  # services to enumerate, defaults to all (optional)
+  services:
+    - deployments
+    - domains
+```
+
+`vercel_api_token` can be created from https://vercel.com/account/tokens. Vercel tokens have no read-only setting, so the available control is scope: a **Team** token (select the team, then **All Projects**) reaches one team and needs no `vercel_team_id`. A **Full Account** token needs `vercel_team_id` to reach a team's projects, and a **Project** token returns only that project.
+
+`deployments` returns the hostnames of each project's latest deployments, not its full deployment history. `domains` returns the aliases on each project's production target, so preview and branch aliases are not included.
+
+References: 
+1. https://vercel.com/docs/accounts/access-tokens
+2. https://vercel.com/docs/rest-api
+
 ## CDN & DNS Management
 
 ### Fastly
 
 Supported Fastly Services:
   - Services
 
 **Example Config:**
 
 Fastly can be integrated by using the following configuration block.
 
 ```yaml
 - # provider is the name of the provider
@@ -466,14 +499,14 @@
 1. https://docs.fastly.com/en/guides/using-api-tokens#creating-api-tokens
 
 
 ### Namecheap
 
 Supported Namecheap Services:
   - Domain List
 
 **Example Config:**
 
 Namecheap can be integrated by using the following configuration block.
 
 ```yaml
 - provider: namecheap # provider is the name of the provider
@@ -485,9 +518,9 @@
   namecheap_user_name: $NAMECHEAP_USER_NAME
 ```
 
 Namecheap API Access can be enabled by visiting https://ap.www.namecheap.com/settings/opensource/apiaccess/ and then:
 - Toggle ON API Access switch
 - Add your public IP to Whitelistted IPs 
 
 
 References: 
@@ -514,19 +547,19 @@
   api_token: $CF_API_TOKEN
 ```
 
 `api_key` can be generated from Cloudflare API Key manager. It needs to be Global API Key due to limitation of cloudflare new API tokens.
 
 References: 
 1. https://developers.cloudflare.com/api/keys
 
 ### Hetzner Cloud
 
 Supported Hetzner Cloud Services:
   - Instances
 
 **Example Config:**
 
 Hetzner Cloud can be integrated by using the following configuration block.
 
 ```yaml
 - provider: hetzner # provider is the name of the provider
@@ -549,7 +582,7 @@
 
 **Example Config:**
 
 To integrate Kubernetes, utilize the configuration block outlined below. This block allows you to specify Kubernetes connection details either through a file path or directly by providing the encoded kubeconfig content. If both kubeconfig_file and kubeconfig_encoded are specified, the kubeconfig_encoded will take precedence.
 
 ```yaml
 - provider: kubernetes # provider is the name of the provider
@@ -567,13 +600,13 @@
 3. https://learn.microsoft.com/en-us/azure/aks/control-kubeconfig-access#get-and-verify-the-configuration-information
 4. https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#store_info
 
 ### Hashicorp Tools
 
 With Cloudlist you can get assets from nomad, consul and terraform. Cloudlist can query Nomad and Consul directly, and will use the Terraform state file to list Terraform created assets.
 
 #### Nomad
 
 Hashicorp Nomad can be integrated by using the following configuration block.
 
 **Example Config:**
 
@@ -600,7 +633,7 @@
 
 #### Consul
 
 Hashicorp Consul can be integrated by using the following configuration block.
 
 **Example Config:**