Expand description
Agentic Resource Discovery (ARD) — client integration.
Adds a resource_discovery capability that lets a running agent discover
external capabilities (MCP servers, A2A agents) through ARD registries and
attach them mid-session. This is the client/consumer side only;
publishing an Everruns catalog + registry endpoint (ARD-as-a-server) is
tracked separately.
Part of the Everruns ecosystem.
use everruns_ard::RESOURCE_DISCOVERY_CAPABILITY_ID;
assert_eq!(RESOURCE_DISCOVERY_CAPABILITY_ID, "resource_discovery");Layering: ARD answers “which MCP server / A2A agent should even be
attached?” — the layer above tool_search (which defers schemas for tools
already attached). Discovery runs outside the model context; attachment
reuses the existing scoped-mcpServers / A2A machinery, so the agent loop
is unchanged (see everruns_core::ard_attachment).
Authentication is connection-backed: registry bearer tokens use the ard connection
provider, falling back to the ARD_REGISTRY_TOKEN session secret/env var for
operator/test use. Anonymous-read registries need no token.
Modules§
- client
- ARD registry REST client and protocol types.
- config
resource_discoverycapability configuration.- connection
- ARD registry connection provider.
- tools
resource_discoverytools:discover_resources,attach_resource,list_attached_resources.
Structs§
Constants§
- CAPABILITY_
PLUGINS - Capability plugins this crate contributes to a hosted catalog.
- CONNECTOR_
PLUGINS - Connector plugins this crate contributes to a hosted catalog.
- RESOURCE_
DISCOVERY_ CAPABILITY_ ID - Capability id wired onto agents (e.g. the “Capability Scout” seed agent).