Export API Keys

The cleanest OpenClaw setup is to provide ChirrOp credentials through environment variables.

Use:

export CHIRROP_API_KEY=chp_your_api_key

That lets OpenClaw tasks, SDK examples, and chirrop-skills use the same runtime credential.

Why use an environment variable

• avoids hard-coding the key in prompts or source files
• works cleanly with OpenClaw task runners and shells
• matches the default resolution path used by the SDKs
• makes local testing and deployment more consistent

Typical usage

In shell-based runs:

export CHIRROP_API_KEY=chp_your_api_key
openclaw run your-task

In code, prefer reading from the environment:

curl -H "Authorization: Bearer $CHIRROP_API_KEY" https://api.chirrop.com/v1.0/events

const client = createClient({ key: process.env.CHIRROP_API_KEY! });

client = new_client(api_key=os.environ["CHIRROP_API_KEY"])

client, err := chirrop.NewClient(chirrop.Options{})

For team environments, treat CHIRROP_API_KEY like any other production secret.