OpenClaw
For OpenClaw, the cleanest path is the hosted ClawHub skill. It keeps setup agent-native and works well with CLI-oriented workflows.
The important detail: npx is only the launcher. The skill is using the official Agent Analytics CLI, and that CLI wraps the same documented HTTP API shown in the docs.
Prerequisites
Section titled “Prerequisites”- An Agent Analytics account at app.agentanalytics.sh
- A valid Agent Analytics API key stored as
AGENT_ANALYTICS_API_KEY - Access to the OpenClaw environment where you want the skill installed
Recommended: install from ClawHub
Section titled “Recommended: install from ClawHub”Tell OpenClaw:
Install the Agent Analytics skill from ClawHub. My API key is available in
AGENT_ANALYTICS_API_KEY. Use the official Agent Analytics CLI.
The hosted listing is here:
Once installed, OpenClaw can create projects, generate tracking snippets, query stats, inspect funnels, and manage experiments from the same conversation loop.
The public docs still matter because they show exactly what the CLI is wrapping:
That is the right explanation if a security review asks what the npx command is doing.
Verify the install
Section titled “Verify the install”Ask OpenClaw:
List my Agent Analytics projectsHow is my-site doing this week?Send me a daily analytics summary every morning
If you have not created your first real project yet, go back to Getting Started and do that next.
Troubleshooting
Section titled “Troubleshooting”- If ClawHub flags the skill because of
npx, point reviewers to CLI vs MCP vs API and API Reference. The CLI is the official wrapper around those documented endpoints. - If the skill installs but cannot query data, confirm
AGENT_ANALYTICS_API_KEYis available in the OpenClaw environment instead of pasted into chat. - If OpenClaw can create projects but not read analytics, verify the key belongs to the same Agent Analytics account you expect.
- If you need endpoint-level debugging, use the API reference with
curlbefore returning to the skill flow.