beacon-APIs VS docs

The clients are already built to conform to the execution API spec and beacon API spec, so building tools to interact with them is already client-agnostic to a great degree. If I add a custom ETH mainnet endpoint to Metamask, it doesn't care what client is providing the endpoint - only that it conforms to the spec.

Our light client API endpoints have now been aligned to the spec discussed at Devconnect in Amsterdam. To see the updated endpoints, refer to the discussion here: https://github.com/ethereum/beacon-APIs/pull/181

If you're hoping to use the Bitwarden app from external public networks it's going to be hard to use Access as there's no way for the app to do that initial authentication. You could try to exclude the paths used by the app (https://github.com/bitwarden/docs/blob/master/api/specs/public/swagger.json) but that kind of defeats the purpose of using Access. I mean, you can fudge a degree of security on by then having firewall rules apply to the API paths, say (so even though they bypass Access you could still block/allow based on country, ASN, IP, user-agent etc). You're kind of now stuck fucking about of the edges of using something not quite fit-for-purpose, mind.