Manifest Reference
Manifests define agent capabilities and constraints. YAML format, schema version 1.0.
Structure
schema_version: "1.0"
name: my-agent
version: "1.0.0"
publisher: example
# UDS mode (cooperative agents)
capabilities:
- name: api-call
# ... capability definition
# OR transparent mode (unmodified agents)
network:
outbound:
# ... network rules
# Common sections
taint_rules:
- name: pii-isolation
# ... taint rule
secrets:
- name: API_KEY
# ... secret definition
settings:
audit_path: /var/log/hull0/audit.jsonl
Modes
Manifests operate in one of two modes:
| Mode | Section | Use Case |
|---|---|---|
| UDS | capabilities | Cooperative agents using Hull0 protocol |
| Transparent | network | Unmodified agents with network rules |
A manifest cannot have both capabilities and network sections.
Sections
- Capabilities - UDS mode API rules
- Network Policy - Transparent mode network rules
- Taint Rules - Data flow constraints
- Secrets - Secret declarations
Example: UDS Mode
schema_version: "1.0"
name: legal-assistant
version: "1.0.0"
publisher: hull0
capabilities:
- name: openai-chat
description: Chat completion API
api:
method: POST
url_pattern: "https://api.openai.com/v1/chat/completions"
rate_limit:
requests_per_minute: 60
secret_headers:
Authorization: "Bearer ${OPENAI_API_KEY}"
secrets:
- name: OPENAI_API_KEY
required: true
Example: Transparent Mode
schema_version: "1.0"
name: web-scraper
version: "1.0.0"
publisher: hull0
network:
outbound:
- name: target-sites
domains: ["*.example.com"]
ports: [443]
protocol: tcp
dns:
mode: allowlist
runtime:
runtime_type: node
entrypoint: "node /app/index.js"