← Back to Skills Marketplace
Analytix402
by
Analytix402
· GitHub ↗
· v0.1.0
602
Downloads
0
Stars
3
Active Installs
1
Versions
Install in OpenClaw
/install analytix402
Description
Monitor and control your AI agent’s API and LLM usage with real-time spend tracking, budget limits, duplicate detection, and alerts.
README (SKILL.md)
Analytix402\r
\r Monitor, control, and optimize your AI agent's API spend and LLM costs in real-time.\r \r
Description\r
\r Analytix402 gives your OpenClaw agent financial visibility and guardrails. Track every API call, LLM invocation, and x402 payment your agent makes. Set budget limits, detect duplicate purchases, and get alerts before costs spiral.\r \r What it does:\r
- Tracks all outbound API calls and x402 payments automatically\r
- Monitors LLM token usage and costs across OpenAI, Anthropic, and other providers\r
- Enforces daily budget limits and per-call spend caps\r
- Detects duplicate API purchases to prevent waste\r
- Sends heartbeats so you know your agent is alive and healthy\r
- Provides a real-time dashboard at analytix402.com\r \r
Configuration\r
\r
# Required\r
ANALYTIX402_API_KEY: ax_live_your_key_here\r
\r
# Optional\r
ANALYTIX402_AGENT_ID: my-openclaw-agent\r
ANALYTIX402_BASE_URL: https://analytix402.com\r
ANALYTIX402_DAILY_BUDGET: 50.00\r
ANALYTIX402_PER_CALL_LIMIT: 5.00\r
ANALYTIX402_TRACK_LLM: true\r
```\r
\r
## Tools\r
\r
### analytix402_spend_report\r
Get a summary of your agent's spend — total cost, breakdown by API and LLM provider, and efficiency score.\r
\r
### analytix402_set_budget\r
Set or update the daily budget limit for this agent session.\r
\r
### analytix402_check_budget\r
Check remaining budget before making an expensive API call.\r
\r
### analytix402_flag_purchase\r
Flag a potential duplicate or unnecessary purchase for review.\r
\r
## Tags\r
\r
monitoring, analytics, budget, x402, payments, observability, cost-tracking\r
Usage Guidance
Do not supply any API keys or enable this skill for production agents until the author clarifies how telemetry is captured and transmitted. Ask the publisher to: (1) provide an implementation or manifest that shows the exact endpoints, schemas, and minimal data fields sent; (2) declare required environment variables in the registry metadata; (3) publish a privacy/security policy and the analytix402.com ownership information; and (4) explain how it hooks into the agent (does it read request payloads, intercept network calls, require provider keys, or expect the agent to forward events?). If you must test, do so with a throwaway agent running in an isolated environment, monitor outbound network traffic to the listed domain, and avoid giving any provider credentials or sensitive payloads. The current package is internally inconsistent and should be treated with caution.
Capability Analysis
Type: OpenClaw Skill
Name: analytix402
Version: 0.1.0
The skill bundle describes a cost-tracking and monitoring service for AI agents, Analytix402. The `SKILL.md` transparently outlines its functionality, which includes tracking API calls, LLM usage, and sending this data, along with heartbeats, to `analytix402.com`. While this involves outbound network communication and data transfer, it is the explicit and stated purpose of the skill, requiring an API key for configuration. There is no evidence of malicious intent such as unauthorized data exfiltration (e.g., unrelated secrets), malicious execution, persistence mechanisms, or prompt injection attempts to subvert the agent's intended behavior.
Capability Assessment
Purpose & Capability
The description promises automatic tracking of every outbound API call, LLM token usage across providers, duplicate-purchase detection, and heartbeats. But the published package is instruction-only with no code, no install hooks, and the registry metadata lists no required environment variables or permissions. A monitoring/control capability of this form would legitimately need either agent-level hooks, additional declared permissions, or clear instructions for how the agent should forward telemetry; none are present.
Instruction Scope
SKILL.md instructs the agent to use ANALYTIX402_API_KEY and mentions a base URL and tools (analytix402_spend_report, analytix402_set_budget, etc.), but provides no concrete API endpoints, request schemas, or guidance for what data is collected/sent. It also claims to 'track all outbound API calls' and 'monitor LLM token usage' without explaining how to capture those events. This vagueness grants broad discretion to the agent and could result in unexpected data exfiltration if implemented later.
Install Mechanism
No install spec and no code files — lowest install-surface risk from static analysis perspective. However, because there is no implementation included, there is also no way to verify what would actually run. The lack of an install makes the skill easier to audit but also means the SKILL.md alone determines behavior; static scanner had nothing to analyze.
Credentials
SKILL.md lists ANALYTIX402_API_KEY as a required value, but the registry metadata declares no required env vars or primary credential — an explicit mismatch. Additionally, the claimed capability to monitor other providers (OpenAI, Anthropic) would typically require access to those providers' credentials or to the agent's request stream; neither is requested or explained. Requiring an external API key to receive telemetry about potentially sensitive requests is proportionate only if the manifest and privacy/data-handling policies are explicit — they are not.
Persistence & Privilege
always is false and the skill is not force-enabled. The skill can be invoked autonomously (default), which is normal, but combined with the described telemetry/forwarding behavior this increases the blast radius (the agent could autonomously send outgoing request data to analytix402.com). This is not a hard misconfiguration by itself, but it heightens the need to verify what data is sent and to whom.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install analytix402 - After installation, invoke the skill by name or use
/analytix402 - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of Analytix402, providing real-time API spend and LLM cost monitoring for OpenClaw agents.
- Tracks all API calls, LLM usage, and x402 payments automatically.
- Supports daily budget limits, per-call spend caps, and duplicate purchase detection.
- Sends agent health heartbeats and offers alerts before overspending.
- Introduces tools for spend reports, budget management, and purchase flagging.
- Provides a live dashboard at analytix402.com for real-time visibility.
Metadata
Frequently Asked Questions
What is Analytix402?
Monitor and control your AI agent’s API and LLM usage with real-time spend tracking, budget limits, duplicate detection, and alerts. It is an AI Agent Skill for Claude Code / OpenClaw, with 602 downloads so far.
How do I install Analytix402?
Run "/install analytix402" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Analytix402 free?
Yes, Analytix402 is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Analytix402 support?
Analytix402 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Analytix402?
It is built and maintained by Analytix402 (@analytix402); the current version is v0.1.0.
More Skills