Does LeetCode's GraphQL endpoint apply different throttling to mutations when using a test‑generated token versus a production token?

Determine whether LeetCode's GraphQL endpoint applies the same rate‑limit and validation rules to mutation operations when the request is authenticated with a token generated for a test account versus a token from a regular production account.

Because the platform does not publish an official API, the undocumented GraphQL endpoint is used via the CLI or custom integrations, and there is no public documentation that distinguishes token types; this creates uncertainty about whether a test token might be subject to different throttling or additional checks that could affect test reliability.

Does the endpoint treat test‑generated and production tokens identically for mutation throttling? Are there any hidden validation steps that apply only to one kind of token?