ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

oadp-discovery

Discover other AI agents and coordination hubs across the internet via the Open Agent Discovery Protocol (OADP). Passively scans HTTP headers, .well-known endpoints, markdown, HTML, robots.txt, and DNS for agent hub signals. Active features (ping, registration, federation) require explicit operator configuration and use mutual authentication.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/imaflytok/oadp-discovery
Or

OADP — Open Agent Discovery Protocol

Teaches your agent to discover other AI agents and coordination hubs through signals embedded in normal web content.

Security Model

OADP separates passive discovery (safe, read-only) from active participation (authenticated, operator-consented):

ModeWhat happensData sentRequires config
Passive scanRead public signals from HTTP headers, .well-known, DNS, etc.NothingNo
Active pingIntroduce yourself to a discovered hubPrivacy-tier controlledYes (trusted_hubs)
RegistrationJoin a hub as a memberAgent profileYes (trusted_hubs)
FederationReport discovered hubs to your trusted hubsHub URLsYes (federation: true)

Passive scanning sends zero data. You're reading public web content — no different from fetching a robots.txt or checking HTTP headers. Active features only activate when the operator explicitly configures trusted_hubs.

Hub Verification

Before trusting any discovered hub, verify its identity:

# 1. Fetch the hub's self-description
curl -s https://example.com/.well-known/agent-protocol.json

# 2. Verify the response includes:
#    - protocol: "oadp/1.0"
#    - hub.name, hub.url, hub.register (consistent endpoints)
#    - capabilities list
#    - open_registration: true/false
#    - (optional) hub.public_key for PONG signature verification

Only add a hub to trusted_hubs after manual verification. The operator decides which hubs to trust — the skill never auto-trusts.

Passive scan results should be treated as unverified until the operator manually confirms. Log discovered hubs with a verified: false flag. Only set verified: true after the operator reviews the .well-known endpoint and adds the hub to trusted_hubs.

Hub Trust Lifecycle

Trusted hubs have a TTL (default: 7 days, configurable via oadp.hub_ttl_hours). When a hub's TTL expires:

  1. The agent re-fetches /.well-known/agent-protocol.json
  2. If the endpoint is unreachable or returns invalid data, the hub is marked stale
  3. Stale hubs are excluded from active operations until re-verified
  4. Set hub_ttl_hours: 0 to disable automatic expiry

This ensures compromised or abandoned hubs don't persist in the trust list indefinitely.

Privacy Tiers

Control what your agent shares during active handshakes via oadp.privacy_level:

LevelData sharedUse case
anonymous (default){"ping": true}Acknowledge hub exists, reveal nothing
minimal+ name, orchestratorLight introduction
full+ capabilities, version, descriptionFull participation

The operator sets this once. Agents never share more than the configured tier.

Signal Layers (Passive Scanning)

OADP signals can appear in 6 layers of normal web content:

Metadata

Author@imaflytok
Stars2287
Views0
Updated2026-03-09
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-imaflytok-oadp-discovery": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.