chore: make reference to ecosystem rpc page (#241)

<!--

Thank you for contributing to the ZKsync Docs!

Before submitting the PR, please make sure you do the following:

- Update your PR title to follow [Conventional
Commits](https://www.conventionalcommits.org/en/v1.0.0/)
- Read the [Contributing
Guide](https://github.com/matter-labs/zksync-docs/blob/main/CONTRIBUTING.md).
- Understand our [Code of
Conduct](https://github.com/matter-labs/zksync-docs/blob/main/CODE_OF_CONDUCT.md)
- Please delete any unused parts of the template when submitting your PR

-->

# Description
- makes reference to ecosystem rpc page in api reference guide

<!-- Please describe what are the changes and what they are solving for
in this PR. -->

## Linked Issues

<!-- If you have any issues this PR is related to, link them here. -->
<!--
Check out
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue
on how to automate linking a GitHub Issue to a PR.
-->

## Additional context

Co-authored-by: Sarah Schwartz <[email protected]>

Author: dutterbutter

content/00.build/70.api-reference/00.index.md

@@ -9,6 +9,10 @@ ZKsync Era seamlessly integrates with the Ethereum ecosystem. To achieve this in
 we support not only the standard <a href="https://ethereum.org/en/developers/docs/apis/json-rpc/" target="_blank">Ethereum JSON-RPC API</a>
 but also introduce L2-specific features that enhance functionality.
 
+ZKsync supports RPC providers that comply with the
+official <a href="https://ethereum.org/en/developers/docs/apis/json-rpc/" target="_blank">Ethereum JSON-RPC API</a> specification.
+You can explore a comprehensive list of supported RPC providers in our [RPC ecosystem page](https://docs.zksync.io/ecosystem/node-providers).
+
 ::callout{icon="i-heroicons-information-circle" color="amber"}
 To ensure a seamless experience, we impose rate limits on both HTTPS and WebSocket APIs.
 Generally, these limits are ample, ranging from 10 to 100 requests per second (RPS) per client.