API keys and authentication
Private keys, OAuth workspaces and immediate revocation.
Create a key
Open API keys, choose the intended workspace, name the key and select its environment. A live key begins with crx_live_; a test key with crx_test_. The full secret is shown during creation. Store it privately and configure limits at creation or in the key's settings.
Send Authorization: Bearer YOUR_KEY to https://api.cyberrxn.com/v1. Use an environment variable in programs instead of committing a key. Do not place a private key in a public website bundle, URL, screenshot or agent prompt.
Environment and permissions
Live and test credentials use separate call allowances. Test keys do not become paid live credit when their quota is exhausted. A credential's effective permission is intersected with its creator's current workspace permissions. Revoking a key or connection takes effect at authentication; retrying the same revoked credential does not help.
The browser dashboard uses first-party OAuth sessions; ChatGPT and Claude use their own OAuth connections. Select the correct workspace during consent. Each connection appears in Applications and can be revoked independently.
Limit the key
A lifetime key-call allowance or expiry is different from a resetting usage policy. Key limits add daily, weekly, monthly or custom call/money policies. Matching key and workspace policies apply together; one permissive policy does not cancel a more restrictive one.
A permission error, exhausted workspace credit and key-policy cap have different codes. Errors describes how to handle them without turning failures into empty search results.