RPC endpoints provide fast, secure, and reliable access to major blockchain networks. With Djuno RPC endpoints, users can tap into a globally distributed network of nodes, facilitating blockchain interactions without the need to run their own nodes. These endpoints support both read and write operations on the blockchain via HTTPS and WebSocket.

This setup allows Djuno to handle the heavy lifting of running blockchain nodes, enabling developers to focus on building their Web3.0 applications. With just a few clicks, they can have their blockchain nodes up and running.

from menu select RPC Endpoints then create endpoints, a modal pops up, set a Blockchain and networks in which you would like to have node.

after few seconds your node will be operational and then you can navigate in that; there you can copy HTTP or WSS access and start using your RPC node.

All RPC endpoints on the selected network, including both read and write capabilities, are available on your node. For more details on each network’s specifications, please refer to ntercom this link

On the Metrics tab, you can see all activity related to a specific endpoint. At a glance, you can see the latest block height (of that particular blockchain), the number of responses served to you in a rolling 30-day period, and the client version

In the Security tab, you'll find that Djuno offers various security features for your endpoint, which caters to a wide range of use cases.

Endpoints, by default, come with token-based authentication enabled, however, you can disable this feature if you wish. Note that disabling token-based authentication allows anyone who knows your hostname to make requests to your endpoint. You can also create multiple authentication tokens, which enables you to add and remove specific authentication tokens. This can be useful for developing teams to better manage endpoint usage or for security measures such as a comprised endpoint.

You can also whitelist hostnames to have access to your endpoint. If the API request arrives without a whitelisted domain name in the Referrer or Origin HTTP header, the request will be denied.

IP whitelisting is another feature that is available to your QuickNode endpoint. You can add up to 25 IP addresses you wish to whitelist for your endpoint. This security feature differs from referrer whitelisting as it takes an IP (e.g., 123.123.123.123)

You may want to mask your endpoint with another name (for example, your branded domain name). Domain masking can help you accomplish this. You'll want to add the domain to the list and then update your domain's CNAME settings to include your endpoint name

to check out flexible pricing see this link