FOR AGENTS

Let agents operate the access gateway

Warded CLI workflows can be executed by OpenClaw, Hermes Agent, and other tools after a human authorizes the Node for an Organization.

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

The human authorizes the Node. The robot operates scoped resources.

Node enrollment establishes Organization ownership once; Ingress creation then uses the scoped Node Credential.

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 ingress new to build pending config, then warded ingress new --commit to submit it
  • →Use warded ingress status and warded ingress doctor to continue or diagnose the setup
Human side

What still belongs to the human owner

Warded is agent-operated, not ownerless. Organization membership and Node authorization remain human-controlled.

  • •Authorize Node enrollment in the browser
  • •Choose the owning Organization
  • •Manage the Organization plan and quota
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.