Blocks API is deprecated

docs/flashbots-auction/advanced/bundle-pricing.md

@@ -33,4 +33,4 @@ The Flashbots builder employs a new algorithm aimed at maximizing block profitab
 
 There could be two potential reasons why your bundles are not being included. The first reason to consider is that the gas price of your bundles might not be higher than that at the tail end of a block. It's recommended to analyze the gas price your bundles are offering by initially simulating the bundles and observing the difference in the coinbase and the gas consumed. If this value is found to be lower than the tail end of recent blocks, it would be necessary to increase your gas price accordingly.
 
-Alternatively, your bundles may not be included due to competition with other searchers targeting the same opportunities. These competitors might be offering a higher gas price than you. To address this, first simulate your bundles to check the gas price they are offering. Log the amount you are paying for a specific opportunity in a specific block. If your bundle is still not included, refer to the [blocks API](https://blocks.flashbots.net/) to identify the bundle that was included in your target block and the gas price they offered.
+Alternatively, your bundles may not be included due to competition with other searchers targeting the same opportunities. These competitors might be offering a higher gas price than you. To address this, first simulate your bundles to check the gas price they are offering. Log the amount you are paying for a specific opportunity in a specific block.

docs/flashbots-auction/advanced/troubleshooting.mdx

@@ -90,9 +90,9 @@ Covers:
 3. Competitors paying more
 ```
 
-[Flashbots bundles adhere to a "blind" auction](/flashbots-auction/overview), where bundle pricing is not released by Flashbots prior to landing on-chain. The winning "bids" are revealed _only_ after the block containing winning bundles is propagated (via the transactions themselves and [blocks-api](https://blocks.flashbots.net/) for recognizing which set of transactions belong to a bundle).
+[Flashbots bundles adhere to a "blind" auction](/flashbots-auction/overview), where bundle pricing is not released by Flashbots prior to landing on-chain. The winning "bids" are revealed _only_ after the block containing winning bundles is propagated.
 
-While you cannot see a competitor's bid in real time, it is possible to look AFTER the fact to:
+While you cannot see a competitor's bid in real time, it is possible to look onchain AFTER the fact to:
 
 1. Identify the exact bundle (if any) that conflicted with yours
 2. Compare the conflicting bundle's `effective priority fee` with your own (to see if you should be bidding more to remain competitive)
@@ -256,11 +256,7 @@ Analyze the timestamps above in relation to when you observe the targeted block
 
 mev-boost is an opt-in system that runs alongside a validator's consensus client. Unless every validator on Ethereum runs mev-boost, some slots cannot be targeted with Flashbots. Additionally, your builder must be connected to the same relay as the proposer for the target slot.
 
-If no bundles are detected in the blocks-api response, check if other blocks from the same validator ever have Flashbots bundles. If no blocks from a particular validator contain Flashbots bundles, it is possible your bundle was not seen by the validator who proposed the block for the target block height.
-
-## New Blocks API fields
-
-New fields have been added to the blocks API to align the API with PoS Ethereum nomenclature. Details can be found in the [Blocks API page](/flashbots-data/blockapi).
+If no blocks from a particular validator contain Flashbots bundles, it is possible your bundle was not seen by the validator who proposed the block for the target block height.
 
 ## Everything checks out, what's next?
 

docs/flashbots-protect/additional-documentation/bundle-cache.md

@@ -1,10 +1,5 @@
-
-
-
-
-
 ---
-title: bundle cache API
+title: Bundle Cache API
 ---
 
 To create a bundle iteratively (e.g. by signing & sending transactions one at a time with Metamask), you can use the bundle cache API to cache signed transactions and retrieve them with a bundle ID.

docs/sidebars.js

@@ -198,6 +198,5 @@ module.exports = {
     "flashbots-auction/advanced/rpc-endpoint",
     "flashbots-protect/additional-documentation/status-api",
     "flashbots-protect/additional-documentation/bundle-cache",
-    "flashbots-data/blockapi",
   ]
 };