api-registry

Use BEFORE writing API config, env setup, auth, LLM client init, or debugging an external service. Returns authoritative source URLs, latest version, and deprecation warnings. Triggers on any named library/API/tool.

Contract for external plugins (build-loop, debugger, research) to consult api-registry during API setup or debug. Reads ~/.api-registry/registry.db; exits silently if absent.

Use when the user asks how a library/API/tool works, requests docs for a named service, or asks about current models/versions/endpoints. Routes via api-registry to Context7 or WebFetch for authoritative answers.