Authentication
Choose the credential required for runtime SDKs, Node plugins, Agent Training Skills, or Mission Control workflows.
Choose a credential
Use one credential based on the integration you are configuring:
- Python or Node runtime →
PERCEPTEYE_API_KEY(pefw_...) - Agent Training Skill or Claude workflow →
PERCEPTEYE_MC_API_KEY(mck_...) - OpenClaw conversation capability → separately enable host access
These credentials are not interchangeable. Configure only the credential used by your integration. Not every integration needs both.
Configuration reference
| Purpose | Environment variable | Prefix | Supported integration |
|---|---|---|---|
| Runtime access | PERCEPTEYE_API_KEY | pefw_... | Python SDK, Node SDK, and Node plugin |
| Mission Control operator access | PERCEPTEYE_MC_API_KEY | mck_... | Agent Training Skill and Claude plugin workflows |
If your integration uses environment variables, configure only the variable for that integration:
PERCEPTEYE_API_KEY=<runtime-key>
PERCEPTEYE_MC_API_KEY=<mission-control-key>
The two lines show the available variable names, not a requirement to configure both credentials.
Runtime integrations
Use PERCEPTEYE_API_KEY with a key beginning with pefw_ for Python and Node runtime integrations.
The Node plugin supports three configuration methods:
- Runtime environment
- Plugin configuration
- CLI login flow
Mission Control workflows
Use PERCEPTEYE_MC_API_KEY with a key beginning with mck_ for the Agent Training Skill and Mission Control operator workflows, including the Claude plugin.
The Claude plugin requires a Mission Control account, Python 3.9 or later, and an HTTPS connection. OpenClaw conversation access is separate from the credential and must be enabled explicitly when a workflow requires it. A valid key does not grant conversation access.
Secure credential handling
Never paste either credential into chat or commit it to a repository. Provide the key through the integration's configured secure mechanism.