openapi VS docs-cardano-org

have a look https://docs.blockfrost.io ! each call has details of what it returns

You can use blockfrost API to do that by looking up the pool metadata. https://docs.blockfrost.io/

But Blockfrost does have a Python API that you could mess around with. There’s still plenty of cool stuff you can do with it.

https://blockfrost.io/ These guys are 3rd party developers who help with IFPS storages and APIs. https://docs.blockfrost.io/ Their docs as well.

https://docs.blockfrost.io/#tag/Cardano-Transactions/paths/~1tx~1submit/post

We are requesting funds from the community for the first time - to build open-source SDKs on top of the API specification, which, too, is open-source. This way, anyone can develop a backend on top of the specification if they don't trust our implementation or are worried about vendor lock-in.

We are going to open source our backend layer, so you can run your own if you do not trust us. The API specification itself is open, so you can just build your own backend too.

here you go: https://github.com/cardano-foundation/docs-cardano-org/blob/main/explore-cardano/what-is-a-hard-fork-combinator.md

In response to the above problem, instead of fixing it, they just removed the respective documentation. Big red flags

We have the hard fork combinator which makes hard forking quite easy. It eliminates the necessity of a switchover block.