API Registry
Local registry of authoritative API and library docs so agents verify integrations against current sources.
Install
claude plugin marketplace add tyroneross/RossLabs-AI-Toolkit
claude plugin install api-registry@rosslabs-ai-toolkitThe Problem
Integration bugs often start before code is written. An agent remembers an old SDK shape, a renamed model, a deprecated environment variable, or a config path from another framework. The result is plausible code that fails late.
API Registry moves source verification to the front of the workflow. The registry stores approved documentation URLs, refresh logs, and lookup commands so build tools can ask “what docs should I trust for this service?” before writing the integration.
What I Built
API Registry gives coding agents a local source-of-truth map for API, library, and tool documentation. Before an agent configures Better Auth, Groq, Neon, Vercel, or another integration, it can look up the authoritative docs instead of relying on stale training data.
Impact
The registry is deliberately local and explicit. It does not try to be a universal search engine. It captures the docs this development environment trusts, keeps them refreshable, and makes source verification cheap enough to use every time an integration appears.
How It Works
The plugin stores registry state under ~/.api-registry/ with SQLite as the source of truth and a YAML mirror for human inspection. Commands cover the full lifecycle: initialize the database, scan local repos for services, add a service, look up sources, route a docs question, refresh stale entries, and list registered APIs by category.
Build Loop and debugger workflows can consult the registry through a bridge contract during assessment and debugging. That makes current docs a normal part of the build loop instead of an emergency search after the first failure.