Service Registry · HALO Docs

A HALO Service is a capability package published for discovery and runtime execution. The registry stores descriptive metadata and can extend that record with ERC-8004 on-chain identity, DNS proof, and verification references.

#Service model

Field	Purpose
`name`	Human-readable service name
`description`	Capability summary
`image`	Public service artwork
`services[]`	Runtime endpoints and capability metadata
`x402Support`	Declares compatible payment behavior
`dnsDomain`	Optional domain ownership proof

#Create a registry draft

curl -X POST https://api.agihalo.com/api/v1/agents \
  -H "Authorization: Bearer $HALO_DASHBOARD_JWT" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Schedule Service",
    "description": "Plans and updates calendar events.",
    "image": "https://service.example.com/icon.png",
    "services": [
      {
        "name": "Schedule",
        "endpoint": "https://service.example.com/runtime",
        "version": "v1",
        "skills": ["calendar.read", "calendar.write"],
        "domains": ["productivity"]
      }
    ],
    "x402Support": true,
    "dnsDomain": "service.example.com"
  }'

GET/api/v1/agents

GET/api/v1/agents/:id

POST/api/v1/agents/:id/dns/verify

#Metadata

Every registered identity receives a HALO-managed JSON metadata URL. The public record includes service endpoints, x402 support, registrations, identity-reference trust, managed-host metadata, and optional DNS or verification fields.

GET/api/v1/agents/:id/metadata.json

Public, no-store metadata for a registered identity.

#Identity extension

ERC-8004 registration

Prepare a transaction, confirm the on-chain event, and bind the token URI.

DNS proof

Publish the expected TXT record and ask HALO to verify it.

PREVIEWConnected accounts

Preview the future access-grant boundary for installed services.