ccflare

🥈Silver

ccflare is a proxy for the Claude API that provides intelligent load balancing across multiple accounts. It tracks every request, response, and rate limit, ensuring you never hit rate limits. Ideal for operations teams managing high-volume API interactions.

845790Updated 1mo ago

Intermediate30min to implementautomation

Saves ~180 min per use

Quick InstallView Source

git clone https://github.com/snipeship/ccflare.git

Works with:

Claude

Overview

About This Skill

https://github.com/snipeship/ccflare/docs/

Use Cases

Automatically distribute API requests across multiple Claude accounts to avoid rate limits.

Monitor and analyze API usage in real-time to optimize costs and performance.

Log and debug API requests and responses for easier troubleshooting.

Maintain conversation context in applications using session-based load balancing.

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/snipeship/ccflare

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

Act as a CC proxy for my Claude API accounts. I need to manage [NUMBER] accounts with the following details: [ACCOUNT DETAILS]. Track their usage, rotate them as needed, and provide me with a daily summary of API calls made, remaining tokens, and any errors encountered. Use this format for the summary: [SUMMARY FORMAT].

Example Output

# Daily CC Proxy Summary

## Account Usage

- **Account 1**: 1,200 tokens used (80% of daily limit)
- **Account 2**: 950 tokens used (63% of daily limit)
- **Account 3**: 1,500 tokens used (100% of daily limit)

## Errors Encountered

- **Account 3**: Rate limit exceeded at 14:30 UTC. Automatically switched to Account 4.

## Recommendations

- Rotate Account 3 for the next cycle as it has reached its daily limit.
- Monitor Account 1 closely as it is approaching its limit.