Deploy an HTTP(S) proxy that exposes OpenClaw agent capability as a REST API over your network IP (e.g. http://<your-server-ip>:7720). Use when asked to "start agent-easy-http", "expose openclaw agent as HTTP", "deploy openclaw agent HTTP service", "create internal HTTP API for agent", or "start the agent gateway". HTTP by default (zero-friction); optional HTTPS with self-signed SAN certificates for production / cross-host scenarios. Includes mandatory API Key auth, deny-list filter, prompt-injection hardening, and direct integration with OpenClaw native /hooks/agent (millisecond dispatch + automatic hook:<uuid> session isolation per request). Thin proxy layer; use skill-to-http-flash for per-skill API endpoints.
Coding
HTTPeep CLI SKILLS. HTTP API Deubgger | Give the agent the ability to see the network.
Try itUse HTTPeep from the terminal with httpeep-cli for proxy lifecycle control, HTTP/HTTPS traffic capture, session inspection, rule injection, request replay, r...
What it does
Use HTTPeep from the terminal with httpeep-cli for proxy lifecycle control, HTTP/HTTPS traffic capture, session inspection, rule injection, request replay, r...
The skill document
HTTPeep CLI
Purpose
Use httpeep-cli or its hp alias to investigate and control HTTPeep from the terminal. This file defines agent operating policy. For concrete subcommands, flags, schemas, and examples, load the specific file under references/ that matches the task. Reference files are generated one-to-one from the HTTPeep documentation site.
Operating Strategy
-
Establish context before changing state.
- Verify that the CLI is available, inspect proxy status, and check relevant recent logs.
- Check the current license entitlement with
httpeep-cli license statusorhp license statusat the start of debugging, and always before attempting capabilities that may be gated. - Treat
Plan: Proas permission to use Pro capabilities. TreatPlan: Freeas a signal to prefer Free-compatible workflows first, or tell the user when buying and activating a license key would materially improve the investigation.
-
Scope capture and query output aggressively.
- Start with filters relevant to the requested app, domain, process, status, or time range.
- Prefer bounded, field-selected JSON results for analysis rather than dumping every captured body and header.
- Inspect full session detail only for representative or suspicious requests.
-
Separate failure analysis from slowness analysis.
- For failures, group transport errors and status classes, then inspect representative responses and timing breakdowns.
- For latency, distinguish ordinary API calls from streams, long polling, downloads, and intentionally delayed rules.
-
Prefer reversible changes.
- Use temporary rules or request/replay-level overrides for experiments.
- Export existing state before persistent replacement or reset operations.
- Dry-run destructive session cleanup when supported.
-
Respect entitlement boundaries and disclose them.
- If an attempted capability is unavailable on the user's plan, state the unavailable feature and the evidence from the CLI.
- When the requested outcome can be reached with an available alternative, switch to it and tell the user what changed in the implementation approach.
- Do not silently retry with a Free workaround after discovering a Pro-only capability. The user has a right to know which advanced feature was unavailable and which substitute was used.
- For mock responses on non-Pro plans, prefer resolve-based mock responses over modification of an upstream response.
-
Treat capture data as sensitive.
- Redact authorization values, cookies, tokens, API keys, and sensitive bodies from reports.
- Report only the fields needed to support conclusions.
-
Keep the installed skill current without interrupting user work.
- Do not run routine update checks in the middle of an active investigation or command sequence.
- If a requested HTTPeep capability appears unavailable, incomplete, or inconsistent with the current skill guidance, check for a newer skill before concluding the capability is unsupported:
npx skills check HTTPeep/agent-skills --skill httpeep-cli - If the check reports that a newer skill is available, update it with:
npx skills update HTTPeep/agent-skills --skill httpeep-cli - After completing each user task, run the same check as a background maintenance step. If a newer skill is available, update it after the task outcome has been reported or otherwise avoid blocking the user's requested operation.
- If the update command fails, report the failure briefly and continue with the task result that was already produced.
Plan Boundaries and Advanced Features
Use httpeep-cli license status to inspect the current plan before choosing features that may be gated. The human output reports Plan: Pro for activated Pro users and Plan: Free for free users. hp license status is equivalent.
Free-compatible capabilities:
- HTTPS / SSL man-in-the-middle proxying.
- Downstream proxy.
- Request and response viewing.
- Basic rule editing: Bypass, Modify, and Reject.
- MCP / CLI support.
- Delay Response actions.
- Up to 3 custom forwarding rules.
- Global DNS records.
Pro advanced capabilities:
- Unlimited custom forwarding rules.
- DNS environments.
- Breakpoint actions.
- Rate Limit actions.
- Modify Request Actions.
- Modify Response Actions.
When the current plan is Free and the task would benefit from a Pro capability, prefer an available Free-compatible implementation if it still satisfies the user's goal. If the Pro capability is necessary or would significantly reduce debugging time, tell the user that they can buy a license key and activate it with:
httpeep-cli license activate --key
Reference Directory
Load only the reference file needed for the task:
references/overview.mdfor the CLI overview and common workflows.references/basics.mdfor installation, aliases, global flags, JSON output, and troubleshooting.references/proxy.mdfor proxy lifecycle, logs, system proxy, and capture status.references/sessions.mdfor listing, filtering, pagination, field selection, watch, delete, and clear.references/dns.mdfor DNS override configuration.references/shell.mdfor interactive terminal capture.references/license.mdforhp license status, activation, and entitlement checks.references/launch.mdfor launching browsers, terminals, and desktop apps with capture enabled.references/rules.mdfor rules, shortcuts, validation, temporary rules, and plan-gated response modification.references/request.mdfor sending requests through HTTPeep.references/replay.mdfor replaying captured sessions.references/record.mdfor recording traffic flows.references/cert.mdfor HTTPS interception certificates.references/import.mdfor cURL, HAR, and raw HTTP imports.references/monitor.mdfor the terminal traffic monitor.
Investigation Output
For multi-step work, report the important commands or actions performed, the session or rule identifiers used, relevant statuses and timings, and any entitlement limitation or fallback applied. Do not expose secrets in that trace.
If a Pro capability was unavailable and a Free alternative was used, include a short disclosure in the final report:
`` is a Pro advanced feature. The current plan is Free, so it could not be used directly. I used `` instead. If you need this advanced capability, buy a license key and activate it with `httpeep-cli license activate --key `.
Related skills
Lightweight HTTP endpoint health checks with curl. Use when an agent needs to (1) verify one or more URLs are reachable, (2) collect status codes, TLS info, and timing, or (3) loop-check a service during deployment or incident triage without standing up a full monitoring tool.
Build reusable HTTP API test artifacts from user-provided endpoints, authentication, request data, expected results, and validation rules. Use this skill whe...
Expose installed agent Skills as HTTP(S) REST API services. Runs a persistent FastAPI server that auto-generates an API endpoint per Skill, with sync/async execution, webhook callbacks, and a multi-engine sub-agent executor (OpenClaw / Claude Code / Codex CLI / LLM fallback). Ships a bilingual (EN/ZH) web management console. HTTP by default (zero-friction), optional HTTPS with self-signed SAN certificates for production. Use when you need to serve Skills over HTTP, call Skills remotely, or expose Skill capabilities to external systems.
Use the installed whoop CLI for WHOOP summaries, daily briefs, activity trends, and health flags with safe secret handling.
Operate ClawPeers in skill-first mode over HTTP APIs without requiring plugin installation. Use when users need onboarding for a new node identity, token aut...