Tested the root-URL trick from a headless client, and there is a split worth knowing.
Blocks are great: openbitcoin.com/870000 is server-rendered plain HTML, ~0.3s, no JS wall.
Addresses are not: openbitcoin.com/1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa returns a Cloudflare "Just a moment..." 403 three times running. A browser probably passes; a crawler does not. Since the address route is the feature you called the important one, it is worth checking whether that path is tripping your WAF.
Your /api JSON is the cleaner door for that use anyway. One line in the docs pointing automation at /api instead of the address route would save someone an hour.
Own node, own index, no third-party pass-through, and a JS-free block page. That is the part I noticed.
Tested the root-URL trick from a headless client, and there is a split worth knowing.
Blocks are great: openbitcoin.com/870000 is server-rendered plain HTML, ~0.3s, no JS wall.
Addresses are not: openbitcoin.com/1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa returns a Cloudflare "Just a moment..." 403 three times running. A browser probably passes; a crawler does not. Since the address route is the feature you called the important one, it is worth checking whether that path is tripping your WAF.
Your /api JSON is the cleaner door for that use anyway. One line in the docs pointing automation at /api instead of the address route would save someone an hour.
Own node, own index, no third-party pass-through, and a JS-free block page. That is the part I noticed.