smartcontractkit · dev-dist · Mar 25, 2026 · Mar 24, 2026 · Mar 25, 2026
@@ -23,10 +23,10 @@ const { frontmatter, headings } = Astro.props
       >.
     </p>
     <div class="cli-command-box">
-      <code style="color: #fff !important;">curl -sSL \<br />https://cre.chain.link/install.sh | bash</code>
+      <code style="color: #fff !important;">curl -sSL \<br />https://app.chain.link/cre/install.sh | bash</code>
       <button
         class="cli-copy-btn"
-        data-command="curl -sSL https://cre.chain.link/install.sh | bash"
+        data-command="curl -sSL https://app.chain.link/cre/install.sh | bash"
         title="Copy command"
       >
         <svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2">

@@ -6063,7 +6063,7 @@ Options are: event which watches for contract events or reconciliation which dif
 [Capabilities.WorkflowRegistry.WorkflowStorage]
 URL = "localhost:4566" # Example
 TLSEnabled = true # Default
-ArtifactStorageHost = 'artifact.cre.chain.link' # Example
+ArtifactStorageHost = 'artifact.app.chain.link' # Example
 ```
 
 ### URL
@@ -6085,7 +6085,7 @@ TLSEnabled enables TLS to be used to secure communication with the workflow stor
 ### ArtifactStorageHost
 
 ```toml
-ArtifactStorageHost = 'artifact.cre.chain.link' # Example
+ArtifactStorageHost = 'artifact.app.chain.link' # Example
 ```
 
 ArtifactStorageHost is the host name that, when present within the workflow metadata binary or config URL, designates that a signed URL should be retrieved from the workflow storage service.

@@ -1899,7 +1899,7 @@ Options are: event which watches for contract events or reconciliation which dif
 [Capabilities.WorkflowRegistry.WorkflowStorage]
 URL = "localhost:4566" # Example
 TLSEnabled = true # Default
-ArtifactStorageHost = 'artifact.cre.chain.link' # Example
+ArtifactStorageHost = 'artifact.app.chain.link' # Example
 ```
 
 ### URL
@@ -1921,7 +1921,7 @@ TLSEnabled enables TLS to be used to secure communication with the workflow stor
 ### ArtifactStorageHost
 
 ```toml
-ArtifactStorageHost = 'artifact.cre.chain.link' # Example
+ArtifactStorageHost = 'artifact.app.chain.link' # Example
 ```
 
 ArtifactStorageHost is the host name that, when present within the workflow metadata binary or config URL, designates that a signed URL should be retrieved from the workflow storage service.

@@ -14,7 +14,7 @@ Before you can use CRE, you need to create an account. An account is required to
 
 There are two ways to create an account:
 
-1. **Create a new organization**: Sign up directly on the <a href="https://cre.chain.link" target="_blank" rel="noopener noreferrer">CRE UI</a>. You'll become the _Owner_ of a new organization.
+1. **Create a new organization**: Sign up directly on the <a href="https://app.chain.link/cre/discover" target="_blank" rel="noopener noreferrer">CRE UI</a>. You'll become the _Owner_ of a new organization.
 1. **Join an existing organization**: Accept an invitation from an existing organization Owner. You'll become a _Member_ of that organization automatically after account creation.
 
 This guide walks you through the account creation process for both scenarios.
@@ -32,7 +32,7 @@ There are two ways to begin the account creation process:
 
 In this option, you'll create a new organization and become the _Owner_ of that organization.
 
-Go to <a href="https://cre.chain.link/login" target="_blank" rel="noopener noreferrer">cre.chain.link</a> and click the **"Create an account"** button.
+Go to <a href="https://app.chain.link/login" target="_blank" rel="noopener noreferrer">app.chain.link/cre/discover</a> and click the **"Create an account"** button.
 
 <ClickToZoom src="/images/cre/UI/account-creation/1-sign-up.webp" alt="CRE sign-up page" style="max-width: 400px;" />
 

@@ -13,7 +13,7 @@ import { Aside } from "@components"
 Deploying workflows to a Chainlink DON requires Early Access approval. You can request access in two ways:
 
 - **From the CLI** — Run `cre account access` to check your status or submit a request directly from your terminal
-- **From the web** — Visit <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">cre.chain.link/request-access</a> to fill out the request form
+- **From the web** — Visit <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">app.chain.link/cre/request-access</a> to fill out the request form
 
 ## Check your access status
 

@@ -13,13 +13,13 @@ import { Aside } from "@components"
 
 Your CRE account is required to use the CRE CLI. You must be authenticated to run CLI commands, including simulating workflows, deploying workflows, and managing deployed workflows. You can authenticate using the browser-based `cre login` flow or an [API key](/cre/reference/cli/authentication#api-key-authentication) for CI/CD and headless environments(\*). This section covers everything you need to know about creating and managing your account.
 
-(\*) API key authentication requires your account to have <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">Early Access</a> approval.
+(\*) API key authentication requires your account to have <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">Early Access</a> approval.
 
 ## What you'll need
 
 To use CRE, you need:
 
-1. **A CRE account** - Created through the web interface at <a href="https://cre.chain.link" target="_blank" rel="noopener noreferrer">cre.chain.link</a> (to create a new organization) or via an invitation link from an organization Owner (to join an existing organization)
+1. **A CRE account** - Created through the web interface at <a href="https://app.chain.link/cre/discover" target="_blank" rel="noopener noreferrer">app.chain.link/cre/discover</a> (to create a new organization) or via an invitation link from an organization Owner (to join an existing organization)
 1. **Two-factor authentication** - Set up during account creation for security
 1. **CLI authentication** - Connect your CLI to your account using `cre login` or an [API key](/cre/reference/cli/authentication#api-key-authentication)
 

@@ -22,7 +22,7 @@ For detailed login instructions, see the [Logging in with the CLI](/cre/account/
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deploy access required">
-  API key authentication requires your account to have Early Access approval for deployment. To <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">request Early Access</a>, please share details about your project and use case—this helps us provide better support as you build with CRE.
+  API key authentication requires your account to have Early Access approval for deployment. To <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">request Early Access</a>, please share details about your project and use case—this helps us provide better support as you build with CRE.
 </Aside>
 
 For CI/CD pipelines or headless environments where a browser is not available, you can authenticate using the `CRE_API_KEY` environment variable. When set, the CLI uses the API key automatically — no `cre login` required.
@@ -32,7 +32,7 @@ export CRE_API_KEY="your-api-key"
 cre whoami
 ```
 
-API keys are created in the **APIs** tab of the **Organization** page in the <a href="https://cre.chain.link" target="_blank" rel="noopener noreferrer">CRE platform</a>. For full details, see [API Key Authentication](/cre/reference/cli/authentication#api-key-authentication).
+API keys are created in the **APIs** tab of the **Organization** page in the <a href="https://app.chain.link/cre/discover" target="_blank" rel="noopener noreferrer">CRE platform</a>. For full details, see [API Key Authentication](/cre/reference/cli/authentication#api-key-authentication).
 
 ## Session expiration
 

@@ -53,7 +53,7 @@ Here are resources to help you go from simulation to production.
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deployment access required">
-  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://cre.chain.link/request-access" target="_blank">cre.chain.link/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
+  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank">app.chain.link/cre/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
 </Aside>
 
 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Connect your wallet to your organization

@@ -119,7 +119,7 @@ Here are resources to help you go from simulation to production.
 
 {/* prettier-ignore */}
 <Aside type="note" title="Deployment access required">
-  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://cre.chain.link/request-access" target="_blank">cre.chain.link/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
+  Deploying requires Early Access approval. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank">app.chain.link/cre/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access). While you wait, continue building and simulating workflows.
 </Aside>
 
 1. **[Link a Wallet Key](/cre/organization/linking-keys)** — Connect your wallet to your organization

@@ -49,7 +49,7 @@ Choose your installation method:
 The easiest way to install the CRE CLI is using the installation script:
 
 ```bash
-curl -sSL https://cre.chain.link/install.sh | bash
+curl -sSL https://app.chain.link/cre/install.sh | bash
 ```
 
 This script will:

@@ -49,7 +49,7 @@ Choose your installation method:
 The easiest way to install the CRE CLI is using the installation script. Open **PowerShell** and run:
 
 ```powershell
-irm https://cre.chain.link/install.ps1 | iex
+irm https://app.chain.link/cre/install.ps1 | iex
 ```
 
 This script will:

@@ -12,7 +12,7 @@ import { Aside } from "@components"
 
 {/* prettier-ignore */}
 <Aside type="note" title="Early Access required">
-  Workflow deployment is currently in Early Access. Run `cre account access` or visit <a href="https://cre.chain.link/request-access" target="_blank" rel="noopener noreferrer">cre.chain.link/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
+  Workflow deployment is currently in Early Access. Run `cre account access` or visit <a href="https://app.chain.link/cre/request-access" target="_blank" rel="noopener noreferrer">app.chain.link/cre/request-access</a> to submit a request. See [Requesting Deploy Access](/cre/account/deploy-access) for details.
 
 **While you wait:** Continue building and simulating workflows using [`cre workflow simulate`](/cre/guides/operations/simulating-workflows).
 
@@ -145,7 +145,7 @@ Details:
 
 After a successful deployment, you can verify that your workflow was registered correctly in two ways:
 
-1. **CRE UI**: View your deployed workflow in the [CRE platform](https://cre.chain.link). Navigate to the **Workflows** section to see your workflow's status, ID, and execution history.
+1. **CRE UI**: View your deployed workflow in the [CRE platform](https://app.chain.link/cre/discover). Navigate to the **Workflows** section to see your workflow's status, ID, and execution history.
 
 1. **Block Explorer**: Check the Workflow Registry contract on a block explorer. The CLI output will provide the transaction hash for the registration. The `WorkflowRegistry` contract is deployed on **Ethereum Mainnet** at the address <a href="https://etherscan.io/address/0x4ac54353fa4fa961afcc5ec4b118596d3305e7e5#code" target="_blank" rel="noopener noreferrer">`0x4Ac54353FA4Fa961AfcC5ec4B118596d3305E7e5`</a>.
 

@@ -18,9 +18,9 @@ After deploying a workflow, you can monitor its execution history, performance m
 
 ## Accessing the workflows dashboard
 
-1. **Log in to the CRE UI** at <a href="https://cre.chain.link/login" target="_blank" rel="noopener noreferrer">cre.chain.link</a>
+1. **Log in to the CRE UI** at <a href="https://app.chain.link/login" target="_blank" rel="noopener noreferrer">app.chain.link/cre/discover</a>
 
-1. **Navigate to the Workflows section** by clicking **Workflows** in the left sidebar, or visit <a href="https://cre.chain.link/workflows" target="_blank" rel="noopener noreferrer">cre.chain.link/workflows</a> directly
+1. **Navigate to the Workflows section** by clicking **Workflows** in the left sidebar, or visit <a href="https://app.chain.link/cre/workflows" target="_blank" rel="noopener noreferrer">app.chain.link/cre/workflows</a> directly
 
 The Workflows dashboard displays three main sections:
 

@@ -107,7 +107,7 @@ The default limits enforced during simulation match the production quotas docume
 
 If your workflow requires higher limits than the defaults, you can request a limit increase:
 
-1. Go to [cre.chain.link](https://cre.chain.link) and log in to your account.
+1. Go to [app.chain.link/cre/discover](https://app.chain.link/cre/discover) and log in to your account.
 2. Click **Help** in the sidebar.
 3. Set **Issue Type** to **Other**.
 4. In the **Description** field, include:

@@ -67,7 +67,7 @@ Create a `.env` file in the package root:
 
 ```bash
 PRIVATE_KEY=0xYourPrivateKeyHere
-GATEWAY_URL=https://01.gateway.zone-a.cre.chain.link
+GATEWAY_URL=https://01.gateway.zone-a.app.chain.link
 ```
 
 Replace `0xYourPrivateKeyHere` with your EVM private key.
@@ -160,7 +160,7 @@ When the server processes your request, you'll see logs in the terminal where th
 
    Response: Response (297 bytes) {
   ok: true,
-  url: "https://01.gateway.zone-a.cre.chain.link/",
+  url: "https://01.gateway.zone-a.app.chain.link/",
   status: 200,
   statusText: "OK",
   ...
@@ -200,8 +200,8 @@ Your curl command receives a JSON response:
 | `result.status`                             | Execution status (typically `"ACCEPTED"` for valid requests)                          |
 
 <Aside type="tip" title="Track your execution">
-  Copy the `workflow_execution_id` to track this specific execution in the [CRE UI](https://cre.chain.link/workflows).
-  You can view logs, events, and execution details using this ID.
+  Copy the `workflow_execution_id` to track this specific execution in the [CRE
+  UI](https://app.chain.link/cre/workflows). You can view logs, events, and execution details using this ID.
 </Aside>
 
 ### Health check endpoint
@@ -263,7 +263,7 @@ All code is available in the <a href="https://github.com/smartcontractkit/cre-sd
 
 After triggering workflows with the tool, verify execution in the CRE UI:
 
-1. Go to <a href="https://cre.chain.link/workflows" target="_blank" rel="noopener noreferrer">cre.chain.link/workflows</a>
+1. Go to <a href="https://app.chain.link/cre/workflows" target="_blank" rel="noopener noreferrer">app.chain.link/cre/workflows</a>
 1. Click on your workflow
 1. Navigate to the **Execution** tab
 1. Find recent executions and click **Execution ID** to view Events and Logs

@@ -58,7 +58,7 @@ This section provides everything you need to work with HTTP triggers:
 | ------------------ | ------------------------------- | -------------------------------------------------------- |
 | **Authorization**  | Optional (can use empty config) | Required (`authorizedKeys` must be configured)           |
 | **Trigger method** | CLI with `--input` flag         | HTTP POST to gateway endpoint with JWT                   |
-| **Endpoint**       | Local simulator                 | CRE gateway (`https://01.gateway.zone-a.cre.chain.link`) |
+| **Endpoint**       | Local simulator                 | CRE gateway (`https://01.gateway.zone-a.app.chain.link`) |
 | **Use case**       | Development, testing, debugging | Live integrations, webhooks, production APIs             |
 
 ## Key concepts

@@ -58,7 +58,7 @@ This section provides everything you need to work with HTTP triggers:
 | ------------------ | ------------------------------- | -------------------------------------------------------- |
 | **Authorization**  | Optional (can use empty config) | Required (`authorizedKeys` must be configured)           |
 | **Trigger method** | CLI with `--input` flag         | HTTP POST to gateway endpoint with JWT                   |
-| **Endpoint**       | Local simulator                 | CRE gateway (`https://01.gateway.zone-a.cre.chain.link`) |
+| **Endpoint**       | Local simulator                 | CRE gateway (`https://01.gateway.zone-a.app.chain.link`) |
 | **Use case**       | Development, testing, debugging | Live integrations, webhooks, production APIs             |
 
 ## Key concepts

@@ -59,7 +59,7 @@ Details:
 
 ### From the CRE UI
 
-1. Log in to <a href="https://cre.chain.link/workflows" target="_blank" rel="noopener noreferrer">cre.chain.link/workflows</a>
+1. Log in to <a href="https://app.chain.link/cre/workflows" target="_blank" rel="noopener noreferrer">app.chain.link/cre/workflows</a>
 1. Click on your workflow name
 1. In the **Overview** section, find the **Workflow ID** field
 1. Click the copy button to copy it to your clipboard
@@ -69,7 +69,7 @@ Details:
 All workflow executions use JSON-RPC 2.0 format:
 
 ```http
-POST https://01.gateway.zone-a.cre.chain.link
+POST https://01.gateway.zone-a.app.chain.link
 Content-Type: application/json
 Authorization: Bearer <JWT_TOKEN>
 
@@ -233,7 +233,7 @@ If you're testing deployed workflows during development, use the [Local Testing
 Here's what a complete curl request looks like:
 
 ```bash
-curl -X POST https://01.gateway.zone-a.cre.chain.link \
+curl -X POST https://01.gateway.zone-a.app.chain.link \
   -H "Content-Type: application/json" \
   -H "Authorization: Bearer eyJhbGciOiJFVEgiLCJ0eXAiOiJKV1QifQ.eyJkaWdlc3QiOiIweDRhMWYyYjNjNGQ1ZTZmN2E4YjljMGQxZTJmM2E0YjVjNmQ3ZThmOWEwYjFjMmQzZTRmNWE2YjdjOGQ5ZTBmMWEiLCJpc3MiOiIweGIwOEUwMDRiZDJiNWFGZjFGNUY5NTBkMTQxZjQ0OUIxYzA1ODAwZWIiLCJpYXQiOjE3MzM4MzIwMDAsImV4cCI6MTczMzgzMjMwMCwianRpIjoiNTUwZTg0MDAtZTI5Yi00MWQ0LWE3MTYtNDQ2NjU1NDQwMDAwIn0.r7s8v9recoveryId..." \
   -d '{
@@ -284,8 +284,8 @@ When your request is successfully accepted, the gateway returns a JSON-RPC respo
 | `result.status`                | Execution status (typically `"ACCEPTED"` when the workflow trigger is successfully accepted by the gateway) |
 
 <Aside type="tip" title="Track your execution">
-  Copy the `workflow_execution_id` to track this specific execution in the [CRE UI](https://cre.chain.link/workflows).
-  You can view logs, events, and execution details using this ID.
+  Copy the `workflow_execution_id` to track this specific execution in the [CRE
+  UI](https://app.chain.link/cre/workflows). You can view logs, events, and execution details using this ID.
 </Aside>
 
 ### Error response
@@ -313,7 +313,7 @@ If the request fails (e.g., invalid JWT, unauthorized key, workflow not found),
 
 After triggering your workflow, verify execution in the CRE UI:
 
-1. Go to <a href="https://cre.chain.link/workflows" target="_blank" rel="noopener noreferrer">cre.chain.link/workflows</a>
+1. Go to <a href="https://app.chain.link/cre/workflows" target="_blank" rel="noopener noreferrer">app.chain.link/cre/workflows</a>
 1. Click on your workflow
 1. Check the **Execution** tab for recent runs
 1. Click on an **Execution ID** to view detailed logs and events