FOR AGENTS

Let agents operate the access gateway

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

Tell your agent this
Use AgentOfMe to protect this management endpoint.
Expected execution path
$agentofme gateway enroll
$agentofme gateway start
$agentofme ingress status / agentofme ingress doctor
$agentofme gateway start or agentofme ingress proxy run
Ownership boundary

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

Gateway enrollment establishes Organization ownership once; Ingress creation then uses the scoped Gateway 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 AgentOfMe.

  • →Ask the owner to choose site, spec, domain, and ports first
  • →Use agentofme ingress new for local diagnostics, create Ingress access in the Website, then run agentofme gateway start
  • →Use agentofme ingress status and agentofme ingress doctor to continue or diagnose the setup
Human side

What still belongs to the human owner

AgentOfMe is agent-operated, not ownerless. Organization membership and Gateway authorization remain human-controlled.

  • •Authorize Gateway 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.