ai-api

Discover LLM models dynamically and route requests by measured performance across providers.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/EndUser123/cc-marketplace --skill ai-api-enduser123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-api
Source: https://github.com/EndUser123/cc-marketplace/tree/main/plugins/cc-skills-ai-api/skills/ai-api
Command: npx skills add https://github.com/EndUser123/cc-marketplace --skill ai-api-enduser123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Multi-provider LLM access is hard due to scattered model catalogs and brittle, hard-coded lists. This Skill enables dynamic model discovery and performance-based curation, simplifying provider choice and routing.

Core Features & Use Cases

  • Dynamic model discovery via live catalogs and live tiered selection to optimize model choices.
  • Deterministic routing and capability-aware selection across tasks like code review, debugging, and documentation.
  • Performance tracking and aggregation to support data-driven model curation.

Quick Start

Use the ai-api skill to run a multi-provider LLM review on your codebase with dynamic model selection.

Frequently Asked Questions about ai-api

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage multi-provider LLM access without hardcoding brittle model lists?

Multi-provider LLM access without hardcoding requires dynamic model discovery via live catalogs. This approach enables deterministic routing and capability-aware selection to optimize provider choices across software engineering tasks.

What is dynamic model discovery for LLM routing?

Dynamic model discovery for LLM routing is the process of using live catalogs to find available models. It replaces static lists with live tiered selection to optimize model choices for tasks like code review and debugging.

Can I use performance benchmarking to curate LLM providers for code review?

Performance benchmarking can curate LLM providers for code review by tracking and aggregating results. This logging mechanism supports data-driven model curation, ensuring deterministic routing selects optimal providers.

Does multi-provider LLM routing work for debugging and documentation tasks?

Multi-provider LLM routing works for debugging and documentation tasks through capability-aware selection. It applies deterministic routing to match specific software engineering task requirements with optimal models.

What is the best way to benchmark LLM performance across multiple providers?

The best way to benchmark LLM performance across multiple providers is using deterministic routing with logging. This enables performance tracking and aggregation to support data-driven model curation without maintaining hard-coded lists.

Why does static LLM provider selection fail during software engineering tasks?

Static LLM provider selection fails during software engineering tasks due to scattered model catalogs and brittleness. Dynamic discovery via live catalogs solves this by enabling performance-based curation and deterministic routing.