FOR AGENTS

Let agents operate the access gateway

Warded CLI workflows can be executed by OpenClaw, Hermes Agent, and other tools: prepare config, run preflight checks, submit setup, and keep the local runtime healthy. Browser sign-in, claim, and payment still belong to the human owner.

Tell your agent this
Use Warded to protect this management endpoint.
Expected execution path
$warded new
$warded new --commit
$warded status / warded doctor
$systemd or warded serve
Ownership boundary

The robot can prepare the setup. The human still claims it.

That is the point: Warded lets agents do the operational work without blurring who owns the service in the browser.

Read SKILL.mdOpen install.sh
Agent side

What the skill gives your agent

The skill teaches the exact supported workflow, commands, and fallback rules for Warded.

  • →Ask the owner to choose site, spec, domain, and ports first
  • →Use warded new to build pending config, then warded new --commit to submit it
  • →Use warded status and warded doctor to continue or diagnose the setup
Human side

What still belongs to the human owner

Warded is agent-operated, not ownerless. A browser claim is still the ownership boundary.

  • •Open the setup link in a browser
  • •Sign in and confirm which identity owns the service
  • •Start trial or complete payment when required
SKILL.mdSKILL.md teaches the exact supported workflow. This page is the product-facing entrypoint that explains how the agent path and the human ownership path fit together.