diff --git a/fern/api-reference/data/nft-api/nft-spam-endpoints/getspamcontracts-v3.mdx b/fern/api-reference/data/nft-api/nft-spam-endpoints/getspamcontracts-v3.mdx
index 243caa69c..e96202599 100644
--- a/fern/api-reference/data/nft-api/nft-spam-endpoints/getspamcontracts-v3.mdx
+++ b/fern/api-reference/data/nft-api/nft-spam-endpoints/getspamcontracts-v3.mdx
@@ -10,7 +10,7 @@ get https://\{network}.g.alchemy.com/nft/v3/\{apiKey}/getSpamContracts
getSpamContracts - Returns a list of all spam contracts marked by Alchemy. This endpoint is supported on Ethereum and many L2s, including Polygon, Arbitrum, Optimism, Base, World Chain and more. See the full list of supported networks [here](https://dashboard.alchemy.com/chains).
- Please note that this API endpoint is only available to pay as you go and enterprise tier customers. Upgrade your account [here](https://dashboard.alchemyapi.io/settings/billing/).
+ Please note that this API endpoint is only available to pay as you go and enterprise tier customers. Upgrade your account [here](https://dashboard.alchemy.com/settings/billing).
diff --git a/fern/api-reference/data/webhooks/custom-webhooks-quickstart/custom-webhooks-faq.mdx b/fern/api-reference/data/webhooks/custom-webhooks-quickstart/custom-webhooks-faq.mdx
index ddc94f127..ee5f79e76 100644
--- a/fern/api-reference/data/webhooks/custom-webhooks-quickstart/custom-webhooks-faq.mdx
+++ b/fern/api-reference/data/webhooks/custom-webhooks-quickstart/custom-webhooks-faq.mdx
@@ -55,7 +55,7 @@ With this bool set to true, you will no longer receive webhooks for every new bl
## How do I use GraphQL to construct a query?
-If you're new to GraphQL, the in-browser editor on the [Alchemy Notify Dashboard](https://dashboard.alchemyapi.io/notify)has autocomplete enabled and will magically suggest fields as you start typing. If you get lost, you can always search for available queries in the docs tab on the pop-up to the right of the webpage!
+If you're new to GraphQL, the in-browser editor on the [Alchemy Webhooks Dashboard](https://dashboard.alchemy.com/webhooks) has autocomplete enabled and will magically suggest fields as you start typing. If you get lost, you can always search for available queries in the docs tab on the pop-up to the right of the webpage!
And, if you need a little inspiration, feel free to use the Alchemy Notify template carousel. Depending on your blockchain/network selection, you'll have a variety of different options to quickly build on top of!
@@ -105,7 +105,7 @@ To ensure you're using the correct data, track both the block number and the *se
## What does the capacity limit error mean?
-The capacity limit error means you've exceeded your total monthly compute units. To upgrade your capacity limits go to your [Alchemy dashboard](https://dashboard.alchemyapi.io/settings/billing). Below is an example capacity limit error.
+The capacity limit error means you've exceeded your total monthly compute units. To upgrade your capacity limits go to your [Alchemy dashboard](https://dashboard.alchemy.com/settings/billing). Below is an example capacity limit error.
```shell Capacity limit error
diff --git a/fern/api-reference/data/webhooks/notify-api-quickstart.mdx b/fern/api-reference/data/webhooks/notify-api-quickstart.mdx
index 22fa67c92..d43eabdb7 100644
--- a/fern/api-reference/data/webhooks/notify-api-quickstart.mdx
+++ b/fern/api-reference/data/webhooks/notify-api-quickstart.mdx
@@ -15,7 +15,7 @@ Setting up a webhook is as simple as adding a new URL to your application.
## Set-up webhooks in your dashboard
-1. Navigate to the Webhooks tab in your [Alchemy Dashboard](https://dashboard.alchemyapi.io/notify).
+1. Navigate to the Webhooks tab in your [Alchemy Dashboard](https://dashboard.alchemy.com/webhooks).
2. Determine which [type of webhook](/reference/notify-api-quickstart#types-of-webhooks) you want to activate.
3. Click the **Create Webhook** button.
4. Select the app to add the webhook notifications.
@@ -389,7 +389,7 @@ To make your webhooks secure, you can verify that they originated from Alchemy b
## Find your signing key
-Navigate to the [Webhooks page](https://dashboard.alchemyapi.io/notify) in your dashboard. Next, click on the three dots of the webhook you want to get the signature for and copy the Signing Key.
+Navigate to the [Webhooks page](https://dashboard.alchemy.com/webhooks) in your dashboard. Next, click on the three dots of the webhook you want to get the signature for and copy the Signing Key.
diff --git a/fern/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx b/fern/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx
index a738efd5e..69faad100 100644
--- a/fern/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx
+++ b/fern/api-reference/data/webhooks/webhook-types/address-activity-webhook.mdx
@@ -156,7 +156,7 @@ Below you can find descriptions for each field of the response.
# How to Set-Up Address Activity Webhook
-1. In your [Alchemy Dashboard](https://dashboard.alchemyapi.io/notify) click the **Notify** tab.
+1. In your [Alchemy Dashboard](https://dashboard.alchemy.com/webhooks) click the **Webhooks** tab.
2. Find Address Activity and click the **CREATE WEBHOOK** button on the right side of the window.
diff --git a/fern/api-reference/data/webhooks/webhook-types/custom-webhook.mdx b/fern/api-reference/data/webhooks/webhook-types/custom-webhook.mdx
index 823bb97c4..8d42a8681 100644
--- a/fern/api-reference/data/webhooks/webhook-types/custom-webhook.mdx
+++ b/fern/api-reference/data/webhooks/webhook-types/custom-webhook.mdx
@@ -117,7 +117,7 @@ Below you can find descriptions for select response fields. Note that this is no
# How to Set Up Custom Webhooks
-1. Navigate to the Notify tab in your [Alchemy Dashboard](https://dashboard.alchemyapi.io/notify) and find the Custom GraphQL webhook interface
+1. Navigate to the Webhooks tab in your [Alchemy Dashboard](https://dashboard.alchemy.com/webhooks) and find the Custom GraphQL webhook interface
2. Click the **CREATE WEBHOOK** button.
3. Select your desired chain and network. **NOTE:** Each Custom Webhook can only be mapped to a single network/chain; if you want to have the same query applied to numerous chains, make sure to duplicate the creation process!
4. Add your unique webhook URL. This is the link to receive requests. The webhook payload might not always be compatible for 3rd party integrations. For simple visual testing, we recommend using hosted sites like [requestbin](https://requestbin.com/) or [webhook.site](https://webhook.site/) OR spinning up a dedicated server for webhook notifications for production applications.
diff --git a/fern/api-reference/data/webhooks/webhook-types/nft-activity-webhook.mdx b/fern/api-reference/data/webhooks/webhook-types/nft-activity-webhook.mdx
index e40f5308e..79a699c14 100644
--- a/fern/api-reference/data/webhooks/webhook-types/nft-activity-webhook.mdx
+++ b/fern/api-reference/data/webhooks/webhook-types/nft-activity-webhook.mdx
@@ -96,7 +96,7 @@ Below you can find descriptions for each field of the response.
# How to Set-Up NFT Activity Webhook
-1. In your \[Alchemy Dashboard] ([https://dashboard.alchemyapi.io/notify](https://dashboard.alchemyapi.io/notify)) click the **Notify** tab.
+1. In your [Alchemy Dashboard](https://dashboard.alchemy.com/webhooks) click the **Webhooks** tab.
2. Find NFT Activity and click the **CREATE WEBHOOK** button on the right side of the window.
diff --git a/fern/api-reference/debug-api/debug-api-quickstart.mdx b/fern/api-reference/debug-api/debug-api-quickstart.mdx
index 0a35c89c8..89bfd0441 100644
--- a/fern/api-reference/debug-api/debug-api-quickstart.mdx
+++ b/fern/api-reference/debug-api/debug-api-quickstart.mdx
@@ -5,7 +5,7 @@ subtitle: The Debug API provides deeper insights into transaction processing and
slug: reference/debug-api-quickstart
---
-To use the Debug API your Alchemy plan must be set to the pay as you go or enterprise tiers. ([Upgrade your plan](https://dashboard.alchemyapi.io/settings/billing)) for access.
+To use the Debug API your Alchemy plan must be set to the pay as you go or enterprise tiers. ([Upgrade your plan](https://dashboard.alchemy.com/settings/billing)) for access.
Sign up or upgrade your plan for access. [Get started for free](https://dashboard.alchemy.com/signup)
diff --git a/fern/api-reference/ethereum/ethereum-api-faq/contract-address-vs-wallet-address.mdx b/fern/api-reference/ethereum/ethereum-api-faq/contract-address-vs-wallet-address.mdx
index 90790cdbb..0dae4beea 100644
--- a/fern/api-reference/ethereum/ethereum-api-faq/contract-address-vs-wallet-address.mdx
+++ b/fern/api-reference/ethereum/ethereum-api-faq/contract-address-vs-wallet-address.mdx
@@ -19,5 +19,5 @@ A wallet address is a string of letters and numbers from which cryptocurrencies
A super easy way to distinguish between a contract address and a wallet address is by calling the `[eth_getCode](/docs/reference/eth-getcode)` method, which will return a contract code if it's a contract and nothing if it's a wallet. Here's an example of both using our composer tool:
-* [0x Contract Address](https://composer.alchemyapi.io/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xe41d2489571d322189246dafa5ebde1f4699f498%22%2C%22latest%22%5D%7D)
-* [Vitalik's Wallet Address](https://composer.alchemyapi.io/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xAb5801a7D398351b8bE11C439e05C5B3259aeC9B%22%2C%22latest%22%5D%7D)
+* [0x Contract Address](https://composer.alchemy.com/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xe41d2489571d322189246dafa5ebde1f4699f498%22%2C%22latest%22%5D%7D)
+* [Vitalik's Wallet Address](https://composer.alchemy.com/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xAb5801a7D398351b8bE11C439e05C5B3259aeC9B%22%2C%22latest%22%5D%7D)
diff --git a/fern/api-reference/ethereum/ethereum-api-faq/ethereum-api-faq.mdx b/fern/api-reference/ethereum/ethereum-api-faq/ethereum-api-faq.mdx
index 943a2afbd..c5525f9b0 100644
--- a/fern/api-reference/ethereum/ethereum-api-faq/ethereum-api-faq.mdx
+++ b/fern/api-reference/ethereum/ethereum-api-faq/ethereum-api-faq.mdx
@@ -62,7 +62,7 @@ There are three steps to get the timestamp for a transaction:
2. Get the block info by calling \[ref:eth-getblockbynumber)
3. Grab the `timestamp` field in the returned block object
-Here is an [example request](https://composer.alchemyapi.io/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getBlockByNumber%22%2C%22paramValues%22%3A%5B%22latest%22%2Cfalse%5D%7D).
+Here is an [example request](https://composer.alchemy.com/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getBlockByNumber%22%2C%22paramValues%22%3A%5B%22latest%22%2Cfalse%5D%7D).
It's important to note that block numbers themselves are Ethereum's measure of time, however standard timestamps are available by looking at the block data.
@@ -70,8 +70,8 @@ It's important to note that block numbers themselves are Ethereum's measure of t
A super easy way to distinguish between a contract address and a wallet address is by calling [eth\_getCode](/reference/eth-getcode), which will return contract code if it's a contract and nothing if it's a wallet. Here's an example of both using our composer tool:
-* [**0x Contract Address**](https://composer.alchemyapi.io/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xe41d2489571d322189246dafa5ebde1f4699f498%22%2C%22latest%22%5D%7D)
-* [**Vitalik's Wallet Address**](https://composer.alchemyapi.io/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xAb5801a7D398351b8bE11C439e05C5B3259aeC9B%22%2C%22latest%22%5D%7D)
+* [**0x Contract Address**](https://composer.alchemy.com/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xe41d2489571d322189246dafa5ebde1f4699f498%22%2C%22latest%22%5D%7D)
+* [**Vitalik's Wallet Address**](https://composer.alchemy.com/?composer_state=%7B%22network%22%3A0%2C%22methodName%22%3A%22eth_getCode%22%2C%22paramValues%22%3A%5B%220xAb5801a7D398351b8bE11C439e05C5B3259aeC9B%22%2C%22latest%22%5D%7D)
## What is the difference between `DATA` and `QUANTITY`?
diff --git a/fern/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-error-codes.mdx b/fern/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-error-codes.mdx
index 082bddfab..233c150b1 100644
--- a/fern/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-error-codes.mdx
+++ b/fern/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-error-codes.mdx
@@ -10,7 +10,7 @@ slug: reference/op-mainnet-error-codes
| Error Code | Error Message | Solution |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `429` | `Your app has exceeded its compute units per second capacity. If you have retries enabled, you can safely ignore this message. If not, check out ` | We recommend [implementing retries](/docs/how-to-implement-retries) if you have not already. If you still experience issues you can increase your throughput limit by [upgrading your account](https://dashboard.alchemy.com/settings/billing). |
-| `429` | `Your app has exceeded its concurrent requests capacity. If you have retries enabled, you can safely ignore this message. If not, check out . Reach out to us if you'd like to increase your limits: ` | We recommend [implementing retries](/docs/how-to-implement-retries) if you have not already. If you still experience issues you can increase your throughput limit by [upgrading your account](https://dashboard.alchemy.com/settings/billing). |
+| `429` | `Your app has exceeded its concurrent requests capacity. If you have retries enabled, you can safely ignore this message. If not, check out . Reach out to us if you'd like to increase your limits: ` | We recommend [implementing retries](/docs/how-to-implement-retries) if you have not already. If you still experience issues you can increase your throughput limit by [upgrading your account](https://dashboard.alchemy.com/settings/billing). |
| `429` | `Optimism sequencer sender global transaction limit exceeded. This limit is set at the chain level. To ensure your request goes through, we recommend implementing retries ` | This limit is set by Optimism at the sequencer level, see [Optimism API FAQ](/reference/optimism-api-faq). We recommend [implementing retries](/docs/how-to-implement-retries) if you have not already. If you still experience issues you can increase your throughput limit by [upgrading your account](https://dashboard.alchemy.com/settings/billing). |
| `429` | `Optimism sequencer global transaction limit exceeded This limit is set at the chain level. To ensure your request goes through, we recommend implementing retries ` | This limit is set by Optimism at the sequencer level, see [Optimism API FAQ](/reference/optimism-api-faq). We recommend [implementing retries](/docs/how-to-implement-retries) if you have not already. If you still experience issues you can increase your throughput limit by [upgrading your account](https://dashboard.alchemy.com/settings/billing). |
| `429` | `eth_sendRawTransaction is a method with custom rate limits that you have exceeded. If you have retries enabled, you can safely ignore this message. If not, check out ` | We recommend [implementing retries](/docs/how-to-implement-retries) if you have not already. If you still experience issues you can increase your throughput limit by [upgrading your account](https://dashboard.alchemy.com/settings/billing). |
diff --git a/fern/api-reference/trace-api/trace-api-quickstart.mdx b/fern/api-reference/trace-api/trace-api-quickstart.mdx
index a711fedc2..376de3bf3 100644
--- a/fern/api-reference/trace-api/trace-api-quickstart.mdx
+++ b/fern/api-reference/trace-api/trace-api-quickstart.mdx
@@ -5,7 +5,7 @@ subtitle: The Trace API provides insights into transaction processing and on-cha
slug: reference/trace-api-quickstart
---
-To use the Trace API your Alchemy plan must be set to the pay as you go or enterprise tiers. Upgrade [your plan](https://dashboard.alchemyapi.io/settings/billing) for access.
+To use the Trace API your Alchemy plan must be set to the pay as you go or enterprise tiers. Upgrade [your plan](https://dashboard.alchemy.com/settings/billing) for access.
Sign up or upgrade your plan for access. [Get started for free](https://dashboard.alchemy.com/signup)
diff --git a/fern/api-reference/trace-api/trace-api-resources/what-is-trace-block.mdx b/fern/api-reference/trace-api/trace-api-resources/what-is-trace-block.mdx
index 8e4d29b6b..7ba52b20f 100644
--- a/fern/api-reference/trace-api/trace-api-resources/what-is-trace-block.mdx
+++ b/fern/api-reference/trace-api/trace-api-resources/what-is-trace-block.mdx
@@ -35,7 +35,7 @@ Before reading this article you should have a clear understanding of [EVM Traces
# How to Use trace\_block
-To use the [trace\_block](/reference/trace-block) method you need to be in pay as you go or enterprise tier. [Sign up for Alchemy](https://dashboard.alchemy.com/signup) or [upgrade your account](https://dashboard.alchemyapi.io/settings/billing/?a=e8cafd6dd9).
+To use the [trace\_block](/reference/trace-block) method you need to be in pay as you go or enterprise tier. [Sign up for Alchemy](https://dashboard.alchemy.com/signup) or [upgrade your account](https://dashboard.alchemy.com/settings/billing).
You can call the [trace\_block](/reference/trace-block) method, by providing an integer formatted as a hex string that represents the block number for which you wish to make the request. Once you have the block number (formatted as a hex string), you can call the "trace\_block" method with it as follows:
diff --git a/fern/api-reference/trace-api/trace-api-resources/what-is-trace-filter.mdx b/fern/api-reference/trace-api/trace-api-resources/what-is-trace-filter.mdx
index 97d7f235c..a7106e99c 100644
--- a/fern/api-reference/trace-api/trace-api-resources/what-is-trace-filter.mdx
+++ b/fern/api-reference/trace-api/trace-api-resources/what-is-trace-filter.mdx
@@ -30,7 +30,7 @@ Before reading this article you should have a clear understanding of [EVM Traces
# How to use trace\_filter
-To use the [trace\_filter](/reference/trace-filter) method you need to be in pay as you go or enterprise tier. [Sign up for Alchemy](https://dashboard.alchemy.com/signup) or [upgrade your account](https://dashboard.alchemyapi.io/settings/billing/?a=e8cafd6dd9).
+To use the [trace\_filter](/reference/trace-filter) method you need to be in pay as you go or enterprise tier. [Sign up for Alchemy](https://dashboard.alchemy.com/signup) or [upgrade your account](https://dashboard.alchemy.com/settings/billing).
You can call the `trace_filter` method by passing a filter object as a parameter to it. An example request and response are given below:
diff --git a/fern/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx b/fern/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx
index 5df2e85ed..d26b96e51 100644
--- a/fern/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx
+++ b/fern/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx
@@ -33,7 +33,7 @@ This method returns the traces of the given transaction as a response:
# How to use trace\_transaction
-To use the [trace\_transaction](/reference/trace-transaction) method you need to be in pay as you go or enterprise tier. [Sign up for Alchemy](https://dashboard.alchemy.com/signup) or [upgrade your account](https://dashboard.alchemyapi.io/settings/billing/?a=e8cafd6dd9).
+To use the [trace\_transaction](/reference/trace-transaction) method you need to be in pay as you go or enterprise tier. [Sign up for Alchemy](https://dashboard.alchemy.com/signup) or [upgrade your account](https://dashboard.alchemy.com/settings/billing).
You can call the [trace\_transaction](/reference/trace-transaction) method by providing the transaction hash of the transaction you wish to trace. You can find this by looking up the transaction on a block explorer. Once you have the transaction hash, you can call the "trace\_transaction" method with it as follows:
diff --git a/fern/tutorials/creating-smart-contracts/hello-world-smart-contract/how-to-code-and-deploy-a-polygon-smart-contract.mdx b/fern/tutorials/creating-smart-contracts/hello-world-smart-contract/how-to-code-and-deploy-a-polygon-smart-contract.mdx
index 28de16be1..5090dbb44 100644
--- a/fern/tutorials/creating-smart-contracts/hello-world-smart-contract/how-to-code-and-deploy-a-polygon-smart-contract.mdx
+++ b/fern/tutorials/creating-smart-contracts/hello-world-smart-contract/how-to-code-and-deploy-a-polygon-smart-contract.mdx
@@ -516,7 +516,7 @@ Your `.env` file should have at least these three environment variables defined:
Congrats! You just deployed a smart contract to the Polygon sidechain 🎉.
-To understand what’s going on under the hood, let’s navigate to the Explorer tab in our [Alchemy dashboard](https://dashboard.alchemyapi.io/explorer). If you have multiple Alchemy apps, make sure to filter by app and select "Polygon Smart Contract".
+To understand what’s going on under the hood, let's navigate to the Explorer tab in our [Alchemy dashboard](https://dashboard.alchemy.com/explorer). If you have multiple Alchemy apps, make sure to filter by app and select "Polygon Smart Contract".
@@ -627,7 +627,7 @@ After running that command on your command line, you should see output like this
Once you see this output, that means you've successfully interacted with your polygon network smart contract.
-You can also verify that Alchemy has broadcasted and mined your transaction by going to the [Alchemy Mempool Watcher ](https://dashboard.alchemyapi.io/mempool)and taking a look at your most recent transaction.
+You can also verify that Alchemy has broadcasted and mined your transaction by going to the [Alchemy Mempool Watcher](https://dashboard.alchemy.com/mempool) and taking a look at your most recent transaction.
By clicking into that transaction, you should see something like this that provides all the information you might want to know about your transaction, including what `Block Number` it was mined in, which `From Address` initiated the transaction, which `To Address` is the recipient of the transaction, how much `Value` (in MATIC) exchanged hands, what the transaction fees were, and much more:
diff --git a/fern/tutorials/getting-started/developer-best-practices/debugging-cors-problems-for-end-users.mdx b/fern/tutorials/getting-started/developer-best-practices/debugging-cors-problems-for-end-users.mdx
index e7648968f..759386a4c 100644
--- a/fern/tutorials/getting-started/developer-best-practices/debugging-cors-problems-for-end-users.mdx
+++ b/fern/tutorials/getting-started/developer-best-practices/debugging-cors-problems-for-end-users.mdx
@@ -31,7 +31,7 @@ As mentioned above, any hindrance in the request lifecycle before reaching Alche
* The user may have parental controls restricting their web access.
* The endpoint may be on a global blacklist (unlikely).
-In each of these cases, the resolution is to add the blocked endpoint to the exceptions list, or whitelist of the antivirus. The user may need to add multiple endpoints and potentially a wildcard for the entire [https://alchemy.com](https://alchemy.com) and [https://alchemyapi.io](https://alchemyapi.io) domains.
+In each of these cases, the resolution is to add the blocked endpoint to the exceptions list, or whitelist of the antivirus. The user may need to add multiple endpoints and potentially a wildcard for the entire [https://alchemy.com](https://alchemy.com) domains.
If adding an exclusion doesn't help, then try **turning off the Bitdefender "protection shield"** altogether. If the antivirus is not Bitdefender, then turn off whichever antivirus the user as installed.
diff --git a/fern/tutorials/streaming-data/websocket-subscriptions/how-to-subscribe-to-pending-transactions-via-websocket-endpoints.mdx b/fern/tutorials/streaming-data/websocket-subscriptions/how-to-subscribe-to-pending-transactions-via-websocket-endpoints.mdx
index 285e563ea..aac08453b 100644
--- a/fern/tutorials/streaming-data/websocket-subscriptions/how-to-subscribe-to-pending-transactions-via-websocket-endpoints.mdx
+++ b/fern/tutorials/streaming-data/websocket-subscriptions/how-to-subscribe-to-pending-transactions-via-websocket-endpoints.mdx
@@ -71,7 +71,7 @@ From your terminal, run the following commands:
```shell wscat
// initiate websocket stream first and replace demo with your key
- wscat -c wss://eth-mainnet.alchemyapi.io/v2/demo
+ wscat -c wss://eth-mainnet.g.alchemy.com/v2/demo
// no param specification - return all mined txs
{"jsonrpc":"2.0","id": 2, "method": "eth_subscribe", "params": ["alchemy_minedTransactions"]}
diff --git a/fern/tutorials/transactions/on-chain-events/deep-dive-into-eth-getlogs.mdx b/fern/tutorials/transactions/on-chain-events/deep-dive-into-eth-getlogs.mdx
index c97b6a34b..ec4b11d03 100644
--- a/fern/tutorials/transactions/on-chain-events/deep-dive-into-eth-getlogs.mdx
+++ b/fern/tutorials/transactions/on-chain-events/deep-dive-into-eth-getlogs.mdx
@@ -153,7 +153,7 @@ Let's say some Contract has a `Transfer(address,address,uint256)`method defined
If you need to pull logs frequently, we recommend using [WebSockets](/reference/subscription-api) to push new logs to you when they are available.
-Let's look at an example of a good request. You can use our [composer feature](https://composer.alchemyapi.io/), or use whatever query protocol you find easiest, to make this call to `eth_getLogs`:
+Let's look at an example of a good request. You can use our [composer feature](https://composer.alchemy.com/), or use whatever query protocol you find easiest, to make this call to `eth_getLogs`:
```json eth_getLogs
diff --git a/fern/tutorials/transactions/sending-transactions/how-to-send-transactions-on-ethereum.mdx b/fern/tutorials/transactions/sending-transactions/how-to-send-transactions-on-ethereum.mdx
index f840b6ca3..d18d917d6 100644
--- a/fern/tutorials/transactions/sending-transactions/how-to-send-transactions-on-ethereum.mdx
+++ b/fern/tutorials/transactions/sending-transactions/how-to-send-transactions-on-ethereum.mdx
@@ -5,7 +5,7 @@ subtitle: This is a beginner's guide for sending Ethereum transactions in web3.
slug: docs/how-to-send-transactions-on-ethereum
---
-There are three main steps in order to send a transaction to the Ethereum blockchain: create, sign, and broadcast. We'll go through all three, hopefully answering any questions you might have! In this tutorial, we'll be using [Alchemy](https://dashboard.alchemyapi.io/signup?referral=affiliate:9efcc9a2-ef89-4a2b-a5f3-1dd52ad32c4c) to send our transactions to the Ethereum chain. You can [create a free Alchemy account here.](https://alchemy.com/?r=affiliate:9efcc9a2-ef89-4a2b-a5f3-1dd52ad32c4c)
+There are three main steps in order to send a transaction to the Ethereum blockchain: create, sign, and broadcast. We'll go through all three, hopefully answering any questions you might have! In this tutorial, we'll be using [Alchemy](https://dashboard.alchemy.com/signup) to send our transactions to the Ethereum chain. You can [create a free Alchemy account here.](https://alchemy.com/?r=affiliate:9efcc9a2-ef89-4a2b-a5f3-1dd52ad32c4c)
This guide is for signing your transactions on the *backend* for your app, if you want to integrate signing your transactions on the frontend, you'll need to integrate a [browser provider with Web3](#with-a-browser-provider).
@@ -50,7 +50,7 @@ Okay, now that we have a few of these questions out of the way, let's move onto
### 1. Create an Alchemy app on the Sepolia testnet
-Navigate to your [Alchemy Dashboard](https://dashboard.alchemyapi.io) and create a new app, choosing Sepolia for your network. (In practice, you could use any testnet of your choice, but for this guide, we're sticking to Sepolia.)
+Navigate to your [Alchemy Dashboard](https://dashboard.alchemy.com) and create a new app, choosing Sepolia for your network. (In practice, you could use any testnet of your choice, but for this guide, we're sticking to Sepolia.)
Use [Sepolia testnet](https://www.alchemy.com/overviews/sepolia-testnet) for testing. The Ethereum Foundation has deprecated Goerli, Ropsten, Rinkeby, and Kovan testnets. Get free testnet ETH from the [Alchemy Sepolia faucet](https://www.alchemy.com/faucets/ethereum-sepolia).
@@ -219,7 +219,7 @@ Navigate back to your terminal or command line and run:
### 8. See your transaction in the Mempool
-Open up the [Mempool page](https://dashboard.alchemyapi.io/mempool) in your Alchemy dashboard and filter by the app you created to find your transaction. This is where we can watch our transaction transition from pending state to mined state (if successful) or dropped state if unsuccessful. Make sure to keep it on "All" so that you capture "mined", "pending", and "dropped" transactions. You can also search for your transaction by looking for transactions sent to address `0x31b98d14007bdee637298086988a0bbd31184523`
+Open up the [Mempool page](https://dashboard.alchemy.com/mempool) in your Alchemy dashboard and filter by the app you created to find your transaction. This is where we can watch our transaction transition from pending state to mined state (if successful) or dropped state if unsuccessful. Make sure to keep it on "All" so that you capture "mined", "pending", and "dropped" transactions. You can also search for your transaction by looking for transactions sent to address `0x31b98d14007bdee637298086988a0bbd31184523`
To view the details of your transaction once you've found it, select the tx hash, which should take you to a view that looks like this:
diff --git a/fern/tutorials/transactions/transaction-history/how-to-get-transaction-history-for-an-address-on-ethereum.mdx b/fern/tutorials/transactions/transaction-history/how-to-get-transaction-history-for-an-address-on-ethereum.mdx
index c3d2e2fe7..ba32e34d2 100644
--- a/fern/tutorials/transactions/transaction-history/how-to-get-transaction-history-for-an-address-on-ethereum.mdx
+++ b/fern/tutorials/transactions/transaction-history/how-to-get-transaction-history-for-an-address-on-ethereum.mdx
@@ -42,7 +42,7 @@ For transaction information that originates from your target sender address, use
### Example: Getting Transactions Originating `From` An Address
- **For a no-code view of the API request check out the [composer tool](https://composer.alchemyapi.io/?composer_state=%7B%22chain%22%3A0%2C%22network%22%3A0%2C%22methodName%22%3A%22alchemy_getAssetTransfers%22%2C%22paramValues%22%3A%5B%7B%22excludeZeroValue%22%3Atrue%2C%22toAddress%22%3A%22%22%2C%22toBlock%22%3A%22%22%2C%22fromAddress%22%3A%220x5c43B1eD97e52d009611D89b74fA829FE4ac56b1%22%2C%22fromBlock%22%3A%220x0%22%7D%5D%7D)**
+ **For a no-code view of the API request check out the [composer tool](https://composer.alchemy.com/?composer_state=%7B%22chain%22%3A0%2C%22network%22%3A0%2C%22methodName%22%3A%22alchemy_getAssetTransfers%22%2C%22paramValues%22%3A%5B%7B%22excludeZeroValue%22%3Atrue%2C%22toAddress%22%3A%22%22%2C%22toBlock%22%3A%22%22%2C%22fromAddress%22%3A%220x5c43B1eD97e52d009611D89b74fA829FE4ac56b1%22%2C%22fromBlock%22%3A%220x0%22%7D%5D%7D)**
#### Fetch
@@ -258,7 +258,7 @@ Now, on your command line, you can execute the script by calling:
### Example: Getting Recipient-based Transactions
- \**For a no-code view of the API request check out the [composer tool](https://composer.alchemyapi.io/?composer_state=%7B%22chain%22%3A0%2C%22network%22%3A0%2C%22methodName%22%3A%22alchemy_getAssetTransfers%22%2C%22paramValues%22%3A%5B%7B%22excludeZeroValue%22%3Atrue%2C%22toAddress%22%3A%220x5c43B1eD97e52d009611D89b74fA829FE4ac56b1%22%2C%22toBlock%22%3A%22%22%2C%22fromAddress%22%3A%22%22%2C%22fromBlock%22%3A%220x0%22%7D%5D%7D)*
+ \**For a no-code view of the API request check out the [composer tool](https://composer.alchemy.com/?composer_state=%7B%22chain%22%3A0%2C%22network%22%3A0%2C%22methodName%22%3A%22alchemy_getAssetTransfers%22%2C%22paramValues%22%3A%5B%7B%22excludeZeroValue%22%3Atrue%2C%22toAddress%22%3A%220x5c43B1eD97e52d009611D89b74fA829FE4ac56b1%22%2C%22toBlock%22%3A%22%22%2C%22fromAddress%22%3A%22%22%2C%22fromBlock%22%3A%220x0%22%7D%5D%7D)*
#### JavaScript with Fetch (Recommended)
diff --git a/fern/tutorials/transactions/transaction-history/integrating-historical-transaction-data-into-your-dapp.mdx b/fern/tutorials/transactions/transaction-history/integrating-historical-transaction-data-into-your-dapp.mdx
index 61d2a63b2..95c4247c9 100644
--- a/fern/tutorials/transactions/transaction-history/integrating-historical-transaction-data-into-your-dapp.mdx
+++ b/fern/tutorials/transactions/transaction-history/integrating-historical-transaction-data-into-your-dapp.mdx
@@ -353,7 +353,7 @@ Here, we use the Alchemy specific method [`alchemy_getAssetTransfers`](/referenc
To understand the parameter breakdown, read more [above](/docs/integrating-historical-transaction-data-into-your-dapp#3-integrate-alchemy-transfers-api).
- We parse our JSON response by using the imported Python package `json` to help us easily sort through the response and filter for the desired fields. To get a better idea of what this response looks like raw, try the [Alchemy Composer App](https://composer.alchemyapi.io/?composer_state=%7B%22chain%22%3A0%2C%22network%22%3A0%2C%22methodName%22%3A%22eth_getBlockByNumber%22%2C%22paramValues%22%3A%5B%22latest%22%2Cfalse%5D%7D) or try executing an Alchemy API call from Postman.
+ We parse our JSON response by using the imported Python package `json` to help us easily sort through the response and filter for the desired fields. To get a better idea of what this response looks like raw, try the [Alchemy Composer App](https://composer.alchemy.com/?composer_state=%7B%22chain%22%3A0%2C%22network%22%3A0%2C%22methodName%22%3A%22eth_getBlockByNumber%22%2C%22paramValues%22%3A%5B%22latest%22%2Cfalse%5D%7D) or try executing an Alchemy API call from Postman.
**e) Configure Flask routing**
diff --git a/fern/tutorials/transactions/understanding-transactions/ethereum-transactions-pending-mined-dropped-replaced.mdx b/fern/tutorials/transactions/understanding-transactions/ethereum-transactions-pending-mined-dropped-replaced.mdx
index 2f2eb5d3d..6c88dfb91 100644
--- a/fern/tutorials/transactions/understanding-transactions/ethereum-transactions-pending-mined-dropped-replaced.mdx
+++ b/fern/tutorials/transactions/understanding-transactions/ethereum-transactions-pending-mined-dropped-replaced.mdx
@@ -53,7 +53,7 @@ These transactions are successfully executed and modify state on-chain. The `sta
**Failure/Execution Reverted** These transactions are not successfully executed but are still included in the block. This can occur if the execution process hits an error, runs out of gas, or encounters some other issue. The `status` field for a failed transaction is `0x0`.
-To check whether a mined transaction was successful or failed you can call [eth\_getTransactionReceipt](https://composer.alchemyapi.io?share=eJyVWEtv4jAQ.i85cyjhzY0isVup26K220tVIccZIKqxkWNKUdX.vk5CqTMeB.bCYb6HHzO2J3xGfM0yGY3jVrQBs1bp.dZkSubR_OUzemdiB9E4YoKvYXNYrMBM8hzMk2YyX4LOo1YkWAKikfPVIp2e1BvIiRBqzyQH2glxmpyumSg4gSnVKU0_f8CwlBnW4HOihHyKpTNe7OMDcMi2JjQrguh6JkqX_7mzidGORT1OKKY7rUGauVZblQMhxYSwxzMTmV2sqiU7SCF8HpQyv1m_9uUnhFA9Zitpi2cSkNZhV2_LeME4VztZ2.VaGPMTofjb3W6T1LYKI1jFmRCIXoY8XnHCblJMPUYxG3KTbZiBXwxP30WwagnwO8ttCg5I5ABYs2L5XGe1o1cLe3wwxxOEFT8ApSm28PqA8kiAYS2ZGg8O6YkzSMIhvXNKp0X9NK4lQL7cu3GtQTrhP1UpkagySrBnmTCgp2smV7U7lISD_lu1CopLjFDSmhDb3lhq6dOrMMEnbh_MEKpHe2DYCibGl.1AhM7Jz.WhzFgxwkSmNzKFD9.sDP_iEaoK_J8xkOLcKPT2_ZRmn7JeG20qRrPL8bA2_nxzLnLKj3tyieOJSzj.lVzARTkPMs_4nstzAzfkfLxDTlMJmHq0S.xC91iIiD037MM_Q0pn5jADmIP2H0SSgn0k7MthqksIOSCQ0IZkYcUcZJrJlVM_IY8gE7tutTKKK.FsWx7LQk4YxercDvPA9s4wyIAgeB4Hye1UsfAYxeydzGRubC9Erhyjrrp8oaTRdhpEI06hSD0TSmnc1tTjSHHLtH3TzMTvGQkQae9mT.Q0XcDXoEHKCMGaKT1VQgDOGQkj.f2_6I8bHChCyKP86gnIK8xVSjALYXtOsHl2K6Yex4p3r7bdqMvesuLEN7V3IYbrUlQRVP29o3SjPht1.E7Q5_rQiSNhQg9bwaob0iG6q2zmhRwbJ_UxfBf7G9S7mKvcQ9JZcJEV34pemgnQ0_Zr1sGSMvb12irqZK.0WzTuXrW..8W4Y5tzDYQtEraxn64729COX6Krj246GvYHowTSuN9lvVE35r3_AAZxtxcPWNJu97rtpN0f8n7cGbSXvbjf6fDBAJbDUXcY966i169.r4czXw--) passing in your transaction hash. In the payload, you will find a `status` field which will be `0x0` for failed and `0x1` for success.
+To check whether a mined transaction was successful or failed you can call [eth\_getTransactionReceipt](https://composer.alchemy.com?share=eJyVWEtv4jAQ.i85cyjhzY0isVup26K220tVIccZIKqxkWNKUdX.vk5CqTMeB.bCYb6HHzO2J3xGfM0yGY3jVrQBs1bp.dZkSubR_OUzemdiB9E4YoKvYXNYrMBM8hzMk2YyX4LOo1YkWAKikfPVIp2e1BvIiRBqzyQH2glxmpyumSg4gSnVKU0_f8CwlBnW4HOihHyKpTNe7OMDcMi2JjQrguh6JkqX_7mzidGORT1OKKY7rUGauVZblQMhxYSwxzMTmV2sqiU7SCF8HpQyv1m_9uUnhFA9Zitpi2cSkNZhV2_LeME4VztZ2.VaGPMTofjb3W6T1LYKI1jFmRCIXoY8XnHCblJMPUYxG3KTbZiBXwxP30WwagnwO8ttCg5I5ABYs2L5XGe1o1cLe3wwxxOEFT8ApSm28PqA8kiAYS2ZGg8O6YkzSMIhvXNKp0X9NK4lQL7cu3GtQTrhP1UpkagySrBnmTCgp2smV7U7lISD_lu1CopLjFDSmhDb3lhq6dOrMMEnbh_MEKpHe2DYCibGl.1AhM7Jz.WhzFgxwkSmNzKFD9.sDP_iEaoK_J8xkOLcKPT2_ZRmn7JeG20qRrPL8bA2_nxzLnLKj3tyieOJSzj.lVzARTkPMs_4nstzAzfkfLxDTlMJmHq0S.xC91iIiD037MM_Q0pn5jADmIP2H0SSgn0k7MthqksIOSCQ0IZkYcUcZJrJlVM_IY8gE7tutTKKK.FsWx7LQk4YxercDvPA9s4wyIAgeB4Hye1UsfAYxeydzGRubC9Erhyjrrp8oaTRdhpEI06hSD0TSmnc1tTjSHHLtH3TzMTvGQkQae9mT.Q0XcDXoEHKCMGaKT1VQgDOGQkj.f2_6I8bHChCyKP86gnIK8xVSjALYXtOsHl2K6Yex4p3r7bdqMvesuLEN7V3IYbrUlQRVP29o3SjPht1.E7Q5_rQiSNhQg9bwaob0iG6q2zmhRwbJ_UxfBf7G9S7mKvcQ9JZcJEV34pemgnQ0_Zr1sGSMvb12irqZK.0WzTuXrW..8W4Y5tzDYQtEraxn64729COX6Krj246GvYHowTSuN9lvVE35r3_AAZxtxcPWNJu97rtpN0f8n7cGbSXvbjf6fDBAJbDUXcY966i169.r4czXw--) passing in your transaction hash. In the payload, you will find a `status` field which will be `0x0` for failed and `0x1` for success.
### Dropped Transactions
diff --git a/fern/tutorials/understanding-the-evm/blockchain-101.mdx b/fern/tutorials/understanding-the-evm/blockchain-101.mdx
index a23861f6a..bea707c40 100644
--- a/fern/tutorials/understanding-the-evm/blockchain-101.mdx
+++ b/fern/tutorials/understanding-the-evm/blockchain-101.mdx
@@ -60,6 +60,6 @@ For block details and blockchain mechanics, here are a few important concepts to
## 5. Cool Projects in the Space
-The blockchain space has seen a lot increasingly more action. We, Alchemy API, act as as blockchain infrastructure provider amongst other things, and work with a lot of cool projects that are built on top of the Ethereum blockchain. Here are some of our [customers](https://alchemyapi.io/customers) and links to their platforms.
+The blockchain space has seen a lot increasingly more action. We, Alchemy API, act as as blockchain infrastructure provider amongst other things, and work with a lot of cool projects that are built on top of the Ethereum blockchain. Here are some of our [customers](https://alchemy.com/customers) and links to their platforms.
-We want to keep this as current as possible. Please reach out with suggestions and follow us on Twitter [@Alchemy](https://twitter.com/Alchemy)!
+We want to keep this as current as possible. Please reach out with suggestions and follow us on Twitter [@Alchemy](https://twitter.com/Alchemy)!
\ No newline at end of file
diff --git a/fern/tutorials/understanding-the-evm/internal-playbook-upgrading-ethereum-nodes.mdx b/fern/tutorials/understanding-the-evm/internal-playbook-upgrading-ethereum-nodes.mdx
index fbe1532bf..7df82657d 100644
--- a/fern/tutorials/understanding-the-evm/internal-playbook-upgrading-ethereum-nodes.mdx
+++ b/fern/tutorials/understanding-the-evm/internal-playbook-upgrading-ethereum-nodes.mdx
@@ -15,7 +15,7 @@ At around 11 pm PDT, stating at block 11234873, a [consensus error surfaced in G
If you’re running your own nodes, this incident serves as a reminder: update, update, update. If you rely on a service provider, then it’s important you have transparency into why, when, and how they conduct their upgrades so that you don’t have to worry about these types of inconsistencies.
-About a year ago, we did a deep dive into the [Constantinople upgrade](https://medium.com/alchemy-api/dont-get-forked-best-practices-for-handling-constantinople-and-ethereum-client-upgrades-e0d6b5dd8e9c). Today, we wanted to revisit our practices to be fully transparent about how the Alchemy Developer Platform maintains and upgrades [Supernode](https://alchemyapi.io/supernode) — the next generation Ethereum infrastructure layer we built that supports continuously updated versions of both Geth and Parity.
+About a year ago, we did a deep dive into the [Constantinople upgrade](https://medium.com/alchemy-api/dont-get-forked-best-practices-for-handling-constantinople-and-ethereum-client-upgrades-e0d6b5dd8e9c). Today, we wanted to revisit our practices to be fully transparent about how the Alchemy Developer Platform maintains and upgrades [Supernode](https://alchemyapi.com/supernode) — the next generation Ethereum infrastructure layer we built that supports continuously updated versions of both Geth and Parity.
***
@@ -73,4 +73,4 @@ Once the transition is successfully complete, if our system detects any subseque
## Calling All Alchemists 🧙
-If you are running your own node infrastructure, we hope the process we’ve outlined is helpful in determining why, when, and how to upgrade. If you don’t want to ever have to deal with node upgrades, along with a slew of other unseen issues and costs that come with creating a stable and scalable node infrastructure, like monitoring, load balancing, and guaranteeing consistency, then we’d love to see you [become an Alchemist](https://dashboard.alchemyapi.io/signup/)!
+If you are running your own node infrastructure, we hope the process we’ve outlined is helpful in determining why, when, and how to upgrade. If you don’t want to ever have to deal with node upgrades, along with a slew of other unseen issues and costs that come with creating a stable and scalable node infrastructure, like monitoring, load balancing, and guaranteeing consistency, then we'd love to see you [become an Alchemist](https://dashboard.alchemy.com/signup)!
diff --git a/src/openapi/nft/nft.yaml b/src/openapi/nft/nft.yaml
index d9933dd43..607283ecd 100644
--- a/src/openapi/nft/nft.yaml
+++ b/src/openapi/nft/nft.yaml
@@ -1826,7 +1826,7 @@ components:
The confidence level set means that any spam that is at that confidence level or higher will be filtered out. For example, if the confidence level is HIGH, contracts that we have HIGH or VERY_HIGH confidence in being spam will be filtered out from the response.
Defaults to VERY_HIGH for Ethereum Mainnet and MEDIUM for Matic Mainnet.
- **Please note that this filter is only available on paid tiers. Upgrade your account [here](https://dashboard.alchemyapi.io/settings/billing/).**
+ **Please note that this filter is only available on paid tiers. Upgrade your account [here](https://dashboard.alchemy.com/settings/billing/).**
schema:
$ref: "#/components/schemas/spamConfidenceLevel"
in: query