claude-codex-api

🥈Silver

Claude Code and Codex configuration management tool for switching API configurations, environment variables, and testing API performance. Benefits operations teams by streamlining API management and ensuring optimal performance.

169150Updated 1mo ago

Intermediate30min to implementautomation

Saves ~30 min per use

Quick InstallView Source

git clone https://github.com/4xian/claude-codex-api.git

Works with:

Claude

Overview

About This Skill

This tool streamlines API configuration management for Claude Code and Codex users by providing one-click switching between multiple API endpoints. It supports JSON, JSON5, YAML, and TOML configuration formats and allows administrators to manage API keys, tokens, URLs, and model selections across different providers. The tool includes network latency testing to measure response times, API availability testing to verify configuration validity, and automatic route optimization that selects the fastest endpoint. System environment variables are automatically configured during setup, and users can manage multiple proxy configurations and timeout settings for different scenarios.

How to Use

["Install the claude-codex-api tool in your development environment using the command: `npm install -g claude-codex-api` or `pip install claude-codex-api`.","Authenticate with your API provider by running: `claude-codex-api auth --api-key [YOUR_API_KEY]` or `claude-codex-api auth --profile [PROFILE_NAME]`.","Switch to the desired environment configuration by executing: `claude-codex-api switch --env [ENVIRONMENT_NAME]` (e.g., 'staging', 'production').","Update the API endpoint or other configurations as needed: `claude-codex-api update --endpoint [NEW_API_ENDPOINT] --service [SERVICE_NAME]`.","Run a performance test to validate the changes: `claude-codex-api test --service [SERVICE_NAME] --iterations 100 --timeout 30`. Review the output for response times, success rates, and errors.","Use the troubleshooting suggestions provided in the output to address any issues. For persistent problems, consult the tool's documentation or support resources."]

Use Cases

Switch between multiple API providers without manually editing configuration files

Test API latency across different endpoint routes to identify the fastest option

Verify API configuration validity before deploying to production

Automatically select and switch to the best-performing API endpoint based on latency metrics

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/4xian/claude-codex-api

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Use the claude-codex-api tool to switch to the [ENVIRONMENT_NAME] environment configuration, update the API endpoint to [NEW_API_ENDPOINT], and test the performance of the [SERVICE_NAME] service. Report back the response time, success rate, and any errors encountered during the test. If errors occur, suggest troubleshooting steps.

Example Output

Successfully switched to the 'staging' environment configuration. Updated the API endpoint to 'https://api.staging.example.com/v2'. Performance test for the 'user-authentication' service completed with the following results:

- Response Time: 125ms (average across 10 requests)
- Success Rate: 98% (2 failures out of 100 requests)
- Errors Encountered: Two 502 Bad Gateway errors during peak load (10:45 AM - 10:50 AM).

Recommended Troubleshooting Steps:
1. Check the load balancer logs for the 'user-authentication' service during the reported timeframe.
2. Verify the health checks for the backend pods in the Kubernetes cluster.
3. Increase the timeout settings in the API gateway configuration from 30s to 45s to accommodate slower responses during high traffic.
4. Monitor the CPU and memory usage of the 'user-authentication' pods to identify potential resource constraints.

Next Steps:
- Apply the recommended timeout adjustment and retest.
- Schedule a maintenance window to review the load balancer and backend service configurations.