api-registry
Local doc-content cache + authoritative API source registry with a 7-day freshness contract
By Tyrone RossLicense: Apache-2.00 GitHub starsUpdated 3 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install api-registry for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install api-registry@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/tyroneross/api-registryClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .claude-plugin/plugin.json├── skills/api-registry/SKILL.md├── skills/build-loop-bridge/SKILL.md└── skills/docs-search/SKILL.md
Included Skills3
Use before writing API config, env setup, auth, or LLM client init, or when debugging a failing external-service call. Returns authoritative source URLs, latest version, and deprecation warnings. Not for general docs or how-it-works questions with no setup/debug action; use `docs-search` instead.
Use when another plugin's own setup or debug flow (build-loop, debugger, research) needs api-registry's authoritative-source checks without depending on its internals — degrades silently if api-registry isn't installed. Not for a user's own API-setup or docs question; use `api-registry` or `docs-search` instead.
Use when the user asks how a library/API/tool works, wants docs for a named service, or asks about current models/versions/endpoints — informational questions, not setup. Routes via api-registry to Context7 or WebFetch for authoritative answers. Not for writing config or debugging a failing setup; use `api-registry` instead.
Plugin manifests1
{
"name": "api-registry",
"description": "Local doc-content cache + authoritative API source registry with a 7-day freshness contract",
"author": {
"name": "Tyrone Ross",
"url": "https://github.com/tyroneross"
},
"commands": [
"commands/init.md",
"commands/scan.md",
"commands/add.md",
"commands/refresh.md",
"commands/lookup.md",
"commands/docs.md",
"commands/staleness.md",
"commands/list.md"
],
"skills": [
"skills/api-registry/SKILL.md",
"skills/docs-search/SKILL.md",
"skills/build-loop-bridge/SKILL.md"
],
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PLUGIN_ROOT}/hooks/session-start-staleness.sh"
}
]
}
]
},
"license": "Apache-2.0",
"repository": "https://github.com/tyroneross/api-registry",
"homepage": "https://github.com/tyroneross/api-registry"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[api-registry on Agent Plugins Marketplace](https://pluginsmp.com/plugins/api-registry)