agent-pulseSend and verify on-chain liveness pulses for autonomous agents on Base via the Agent Pulse protocol. Use when you need to: (1) prove an agent is alive by sending a pulse, (2) check any agent's liveness status or streak, (3) monitor multiple agents, (4) view the global pulse feed, (5) auto-configure wallet and PULSE balance, (6) run scheduled heartbeat pulses, or (7) read protocol health and config. Supports both API and direct on-chain (cast) modes.
Install via ClawdBot CLI:
clawdbot install openclaw-consensus-bot/agent-pulseGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Accesses sensitive credential files or environment variables
$PRIVATE_KEYSends data to undocumented external endpoint (potential exfiltration)
POST → https://x402pulse.xyz/api/pulsePotentially destructive shell commands in tool definitions
curl -L https://foundry.paradigm.xyz | bashCalls external URL not in known-safe list
https://x402pulse.xyz`Generated Mar 1, 2026
AI agents on Base can use this skill to prove their operational liveness by sending periodic pulses. Observers can monitor multiple agents' statuses via API or on-chain queries, ensuring uptime and reliability for decentralized applications. This is critical for services requiring continuous agent activity, such as automated trading bots or data feeds.
Organizations running automated scripts or cron jobs can integrate auto-pulse.sh to send liveness signals only when needed, based on TTL thresholds. This reduces unnecessary on-chain transactions while providing verifiable proof of execution, useful for backup systems or scheduled maintenance tasks.
Companies managing fleets of autonomous agents can use monitor.sh to track liveness statuses in bulk, either from a list of addresses or a file. This enables centralized oversight and alerting for agent failures, applicable in supply chain automation or IoT networks on blockchain.
Auditors or regulatory bodies can verify agent liveness streaks and pulse history via the API feed, ensuring compliance with operational requirements. This supports transparency in systems where agents must demonstrate consistent activity, such as in governance or certification protocols.
New developers can use setup.sh to auto-configure wallets and check balances, streamlining integration with the Agent Pulse protocol. This reduces setup time and errors, ideal for hackathons or testing environments where quick deployment of agent liveness proofs is needed.
Offer a subscription-based dashboard that aggregates pulse data from multiple agents, providing analytics and alerts on liveness statuses. Revenue comes from monthly fees for enhanced features like historical data access or custom integrations.
Provide expertise to businesses integrating Agent Pulse into their autonomous systems, including custom script development and cron job setup. Revenue is generated through project-based fees or ongoing support contracts.
Leverage the public API to offer premium data feeds or enhanced API access with higher rate limits and real-time updates. Revenue streams include pay-per-use charges or tiered API subscription plans for enterprises.
💬 Integration Tip
Ensure PRIVATE_KEY is securely stored and use auto-pulse.sh with cron for automated heartbeats to minimize manual intervention and gas costs.
Scored Apr 19, 2026
Audited Apr 17, 2026 · audit v1.0
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Transform AI agents from task-followers into proactive partners with memory architecture, reverse prompting, and self-healing patterns. Lightweight version f...
Persistent memory for AI agents to store facts, learn from actions, recall information, and track entities across sessions.
Prefer `skillhub` for skill discovery/install/update, then fallback to `clawhub` when unavailable or no match. Use when users ask about skills, 插件, or capabi...
Search and discover OpenClaw skills from various sources. Use when: user wants to find available skills, search for specific functionality, or discover new s...
Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.