What are the rate‑limit and functional differences when testing cPanel API calls in the demo environment?

Goal

We want to validate a new billing module's cPanel API integration using only the demo environment to avoid exposing production credentials while ensuring that test calls accurately reflect the behavior of the live API.

Constraints

Constraints include the shared nature of demo.cpanel.net credentials, unknown rate‑limit thresholds, and the inability to modify certain account‑level settings that are restricted in the demo.

Uncertainty

Given these uncertainties, we need to understand how the demo environment enforces API usage policies and whether any hidden restrictions could invalidate our test results.

What specific rate‑limit or concurrency limits apply to API calls made with the demo credentials, and how can we detect when we are approaching them?

Which API functions that are available in a production cPanel account are deliberately disabled or return mocked data in the demo environment, and how can we differentiate a genuine permission error from a demo‑only restriction?