Why can a free account key be refused?

A signed-in free account with a verified email can create one developer key. ClearRun refuses a key when the email is not verified, when the account already has one, or when the key is not a free developer key.

Last updated November 9, 2026

The one key you can create

Sign in at api.clearrun.net/account/keys. Google, GitHub and the email link verify the address when sign-in completes. The full key is shown once and starts with crun_. It calls evaluate, score and chat. Signed-in chat and Paste Check on the site do not use this key.

What that key returns

Score, grade, risk and a summary of 16 words or fewer. Component signals are limited to Evidence support and Reasoning integrity. Chain verification and audit export still need Pro or higher.

Usage cap

The default cap is 2 requests a second, 6 a minute, 30 an hour and 40 a day. Evaluate, score and chat share it. Over the cap, the route returns 429 and a Retry-After header. Calls still spend the free plan's 30 monthly credits.

When a key is refused

Unverified email. 403 with code EMAIL_NOT_VERIFIED.
Second key. A free account can hold one active developer key. Revoke it before creating another.
Not a developer key. A key that is not a free developer key gets 403 with code API_ACCESS_REQUIRED. This includes a key left from a paid plan.

The API access switch

On Pro, Business and Enterprise, turning API access off returns 403 with code API_ACCESS_DISABLED. That switch does not turn a free developer key on or off. Revoke the key to stop it.