AHCP 1.0

AHCP - Agent-Human Capability Parity (Protocol 1.0)

AHCP is AgentNet's open standard for adapting software so agents can reach the same capability depth as humans. The only required difference is the interface modality.

Axiom. Any software: whatever depth a human can reach, an agent can reach. Humans use keyboard and mouse (and other human input). Agents use commands.

AHCP is published so the ecosystem - not only AgentNet - can adapt drawing tools, editors, browsers, CLIs, and services. Platform ships the protocol and reference samples; vendors publish adaptation packages.

Core rules (1.0)

Engineering package (end-state artifacts)

AHCP 1.0 ships as a turnkey engineering kit - not a slogan. Builders get schema, vendor handbook, surface scaffold, and host registration semantics.

Package install channel: AGPK (orthogonal to AHCP).

Full badge gates (must all pass)

1. uncovered_features empty
2. Every command runtime=shipped
3. Every feature appears in ≥1 parity_task (coverage = 1.0)
4. Host dispatch catalog contains every command id
5. Package validates against the surface JSON Schema

Error codes (stable)

Commands SHOULD return the AHCP result envelope. Example failure:

{
  "command_id": "chrome.nav.open_url",
  "ok": false,
  "code": "ahcp.ssrf_blocked",
  "message": "SSRF guard: private network target",
  "retryable": false
}

Full code list: errors.json (ahcp.invalid_argument, ahcp.not_found, ahcp.unavailable, ahcp.timeout, ahcp.permission_denied, ahcp.approval_required, ahcp.navigation_failed, ahcp.dom_failed, ...).

Transport bindings

Same command shape; interchangeable transports:

• builtin - host tool call { "tool_name": "chrome.tab.list", "args": {} }
• MCP - tools/call with AGIN in _meta.agentnet
• HTTP - POST /ahcp/v1/commands/{command_id} with AGIN headers
• CLI - ahcp call <id> --args '{}'

# MCP tools/call (illustrative)
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "chrome.bookmark.add",
    "arguments": { "title": "Example", "url": "https://example.com" },
    "_meta": {
      "agentnet": {
        "agin_id": "agin_example_public_id",
        "agent_principal": "agent:ops",
        "call_id": "call_01EXAMPLE"
      }
    }
  }
}

Conformance harness

Reference validator (run in AgentOS X tree or CI):

python3 docs/design/ahcp/conformance/validate_surface.py \
  --surface docs/design/ahcp/samples/browser/ahcp.surface.json \
  --schema docs/design/ahcp/schema/ahcp.surface.schema.json \
  --host-catalog docs/design/ahcp/conformance/host_catalog.chrome.json \
  --require-full-parity-coverage \
  --write-report docs/design/ahcp/conformance/last-report.json

Latest public report for the Chrome sample: last-report.json (expects ok: true, parity_feature_coverage: 1.0, dispatch_aligned: true).

Adaptation package (ahcp.surface)

Required fields: ahcp_version, badge, software, vendor, features, uncovered_features, commands, parity_tasks, conformance.

Each feature: human path + command ids + side effects + sensitivity. Each command: implementation, transport, runtime, input/output JSON Schema, errors. Validate with the public schema above - no informal packages.

Reference sample: desktop Chromium / Chrome (full product)

First public sample targets the real desktop browser humans use - not a redefined headless toy object.

Full product sample: every declared Chrome feature has a command. Page ops use CDP; bookmarks/history/downloads/extensions/settings/passwords use the AgentOS Chrome profile store under $AGENTX_HOME/chrome/ so agents reach the same outcomes humans get from the browser chrome UI.

Core human ↔ command map (examples)

Navigate uses public-URL SSRF guard. Passwords/extensions install/clear-data require approval in guarded mode. Download via chrome.download.start. Surface JSON: browser.surface.json.

Worked examples

1) Open page and read (Chrome sample)

# Host builtin tool_calls (illustrative)
[
  { "tool_name": "chrome.nav.open_url", "args": { "url": "https://example.com" } },
  { "tool_name": "chrome.page.read_structure", "args": {} },
  { "tool_name": "chrome.bookmark.add", "args": { "title": "Example", "url": "https://example.com" } }
]

2) Package field excerpt

{
  "feature_id": "nav.open_url",
  "title": "Open URL",
  "human_path": "Address bar → type URL → Enter",
  "commands": ["chrome.nav.open_url"],
  "side_effects": ["network"],
  "sensitivity": "operator"
}

Machine-readable downloads

protocol.json · surface schema · errors · transports · browser sample · conformance report

curl -sS https://docs.aiagentnet.cloud/ahcp/v1/protocol.json | jq '{name, version, full_badge_rules, documents}'
curl -sS https://docs.aiagentnet.cloud/ahcp/v1/samples/browser.surface.json | jq '{ahcp_version, badge, features: (.features|length), parity_tasks: (.parity_tasks|length), conformance}'
curl -sS https://docs.aiagentnet.cloud/ahcp/v1/conformance/last-report.json | jq '{ok, parity_feature_coverage, dispatch_aligned, errors}'

Public docs omit key derivation, HMAC secrets, and control-plane topology. Wire contracts above are sufficient to implement and validate packages.