ZES-provider-manager

Manage LLM provider discovery and configuration across API endpoints and free model tiers.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-provider-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ZES-provider-manager
Source: https://github.com/ZESCODE/Zes-Orchestration-System/tree/main/.agents/skills/ZES-provider-manager
Command: npx skills add https://github.com/ZESCODE/Zes-Orchestration-System --skill zes-provider-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves the complexity of managing multiple LLM providers, API keys, and model endpoints by centralizing them through a single, unified gateway.

Core Features & Use Cases

  • Centralized Routing: Manage connections to Groq, OpenAI, Anthropic, Gemini, and free tier models from one configuration file.
  • Provider Discovery: Automatically detect and verify available model endpoints and status.
  • Use Case: When switching between high-performance models like GPT-4o and free alternatives like DeepSeek, use this Skill to update your routing configuration without manually editing individual agent files.

Quick Start

Use the ZES-provider-manager skill to verify the current status of all active LLM providers and their respective gateways.

Frequently Asked Questions about ZES-provider-manager

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

FAQPage Schema
How do I centrally manage LLM routing across multiple API endpoints?

To centrally manage LLM routing, you can use this Skill to unify connections to Groq, OpenAI, Anthropic, and Gemini through a single gateway configuration file, replacing manual agent file edits.

What is the best way to configure fallback logic for free tier LLM models?

Configuring fallback logic for free tier LLM models is handled through this Skill's gateway administration, which facilitates routing between high-performance models and free alternatives like DeepSeek.

How does provider discovery work for diverse LLM API endpoints?

Provider discovery automatically detects and verifies the status of available model endpoints across your configured API keys, maintaining consistent model access for the orchestration system.

Do I need 9Router to maintain consistent model access?

Yes, you need 9Router integration along with local configuration files to maintain consistent model access and successfully execute the gateway administration and routing logic.

Can I switch between GPT-4o and DeepSeek without manually editing agent files?

Yes, you can switch between GPT-4o and DeepSeek by updating your routing configuration through this unified gateway, which overrides the need to manually edit individual agent files.

Why does LLM provider routing fail to verify available model endpoints?

LLM provider routing fails to verify available model endpoints when local configuration files lack proper API keys or when the 9Router integration required for the ZES orchestration system is missing.