service-registry

## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Core Concepts](#core-concepts) - [Service Configuration](#service-configuration) - [Execution Result](#execution-result) - [Quick Start](#quick-start) - [Register Services](#register-services) - [Execute via Service](#execute-via-service) - [Health Checks](#health-checks) - [Service Selection](#service-selection) - [Auto-Selection](#auto-selection) - [Failover Pattern](#failover-pattern) - [Integration Pattern](#integration-pattern) - [Detailed Resources](#detailed-resources) - [Exit Criteria](#exit-criteria) # Service Registry ## Overview A registry pattern for managing connections to external services. Handles configuration, health checking, and execution across multiple service integrations. ## When To Use - Managing multiple external services. - Need consistent execution interface. - Want health monitoring across services. - Building service failover logic. ## When NOT To Use - Single service integration without registry needs ## Core Concepts ### Service Configuration ```python @dataclass class ServiceConfig: name: str command: str auth_method: str # "api_key", "oauth", "token" auth_env_var: str quota_limits: dict models: list[str] = field(default_factory=list) ``` **Verification:** Run the command with `--help` flag to verify availability. ### Execution Result ```python @dataclass class ExecutionResult: success: bool stdout: str stderr: str ...