hex-rate-limits
Implement Hex rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Hex. Trigger with phrases like "hex rate limit", "hex throttling", "hex 429", "hex retry", "hex backoff".
Best use case
hex-rate-limits is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement Hex rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Hex. Trigger with phrases like "hex rate limit", "hex throttling", "hex 429", "hex retry", "hex backoff".
Teams using hex-rate-limits should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hex-rate-limits/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hex-rate-limits Compares
| Feature / Agent | hex-rate-limits | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement Hex rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Hex. Trigger with phrases like "hex rate limit", "hex throttling", "hex 429", "hex retry", "hex backoff".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Hex Rate Limits
## Overview
Hex's API enforces tight limits on project run triggers (20 per minute, 60 per hour) while leaving read operations like status checks and project listing largely unthrottled. Data teams scheduling batch analytics runs or triggering parameterized notebooks from CI/CD pipelines must carefully manage the hourly cap, since a single pipeline triggering 15 projects can consume a quarter of the hourly budget. Polling run status is free, but triggering runs is the bottleneck that shapes integration architecture.
## Rate Limit Reference
| Endpoint | Limit | Window | Scope |
|----------|-------|--------|-------|
| RunProject (trigger) | 20 req | 1 minute | Per API token |
| RunProject (trigger) | 60 req | 1 hour | Per API token |
| GetRunStatus | No hard limit | - | Per API token |
| ListProjects | No hard limit | - | Per API token |
| CancelRun | No hard limit | - | Per API token |
## Rate Limiter Implementation
```typescript
class HexRateLimiter {
private minuteTokens: number = 20;
private hourlyTokens: number = 60;
private lastMinuteRefill: number = Date.now();
private lastHourlyRefill: number = Date.now();
private queue: Array<{ resolve: () => void }> = [];
async acquire(): Promise<void> {
this.refill();
if (this.minuteTokens >= 1 && this.hourlyTokens >= 1) {
this.minuteTokens -= 1;
this.hourlyTokens -= 1;
return;
}
return new Promise(resolve => this.queue.push({ resolve }));
}
private refill() {
const now = Date.now();
this.minuteTokens = Math.min(20, this.minuteTokens + ((now - this.lastMinuteRefill) / 60_000) * 20);
this.lastMinuteRefill = now;
this.hourlyTokens = Math.min(60, this.hourlyTokens + ((now - this.lastHourlyRefill) / 3_600_000) * 60);
this.lastHourlyRefill = now;
while (this.minuteTokens >= 1 && this.hourlyTokens >= 1 && this.queue.length) {
this.minuteTokens -= 1;
this.hourlyTokens -= 1;
this.queue.shift()!.resolve();
}
}
}
const runLimiter = new HexRateLimiter();
```
## Retry Strategy
```typescript
async function hexRunWithRetry(
projectId: string, params: Record<string, any>, maxRetries = 3
): Promise<any> {
for (let attempt = 0; attempt <= maxRetries; attempt++) {
await runLimiter.acquire();
const res = await fetch(`${HEX_BASE}/api/v1/run/${projectId}`, {
method: "POST", headers,
body: JSON.stringify({ inputParams: params }),
});
if (res.ok) return res.json();
if (res.status === 429) {
const delay = 30_000 * Math.pow(2, attempt) + Math.random() * 5000;
await new Promise(r => setTimeout(r, delay));
continue;
}
if (res.status >= 500 && attempt < maxRetries) {
await new Promise(r => setTimeout(r, Math.pow(2, attempt) * 3000));
continue;
}
throw new Error(`Hex API ${res.status}: ${await res.text()}`);
}
throw new Error("Max retries exceeded");
}
```
## Batch Processing
```typescript
async function batchRunProjects(projects: Array<{ id: string; params: any }>, batchSize = 5) {
const results: any[] = [];
for (let i = 0; i < projects.length; i += batchSize) {
const batch = projects.slice(i, i + batchSize);
const runs = await Promise.all(
batch.map(p => hexRunWithRetry(p.id, p.params))
);
// Poll for completion
for (const run of runs) {
let status = run;
while (status.status === "RUNNING") {
await new Promise(r => setTimeout(r, 5000));
const res = await fetch(`${HEX_BASE}/api/v1/run/${run.runId}/status`, { headers });
status = await res.json();
}
results.push(status);
}
if (i + batchSize < projects.length) await new Promise(r => setTimeout(r, 15_000));
}
return results;
}
```
## Error Handling
| Issue | Cause | Fix |
|-------|-------|-----|
| 429 on RunProject | Exceeded 20/min or 60/hour trigger limit | Queue runs, space 5s apart minimum |
| Run stuck in RUNNING | Long-running query or compute timeout | Poll up to 30 min, then CancelRun |
| 401 on scheduled run | API token rotated | Refresh token in CI secrets before batch |
| Empty run output | Project has no published outputs | Verify project has published cells |
| 409 concurrent run | Same project triggered twice | Check run status before re-triggering |
## Resources
- [Hex API Documentation](https://learn.hex.tech/docs/api/api-overview)
## Next Steps
See `hex-performance-tuning`.Related Skills
workhuman-rate-limits
Workhuman rate limits for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman rate limits".
wispr-rate-limits
Wispr Flow rate limits for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr rate limits".
windsurf-rate-limits
Understand and manage Windsurf credit system, usage limits, and model selection. Use when running out of credits, optimizing AI usage costs, or understanding the credit-per-model pricing structure. Trigger with phrases like "windsurf credits", "windsurf rate limit", "windsurf usage", "windsurf out of credits", "windsurf model costs".
webflow-rate-limits
Handle Webflow Data API v2 rate limits — per-key limits, Retry-After headers, exponential backoff, request queuing, and bulk endpoint optimization. Use when hitting 429 errors, implementing retry logic, or optimizing API request throughput. Trigger with phrases like "webflow rate limit", "webflow throttling", "webflow 429", "webflow retry", "webflow backoff", "webflow too many requests".
vercel-rate-limits
Handle Vercel API rate limits, implement retry logic, and configure WAF rate limiting. Use when hitting 429 errors, implementing retry logic, or setting up rate limiting for your Vercel-deployed API endpoints. Trigger with phrases like "vercel rate limit", "vercel throttling", "vercel 429", "vercel retry", "vercel backoff", "vercel WAF rate limit".
veeva-rate-limits
Veeva Vault rate limits for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva rate limits".
vastai-rate-limits
Handle Vast.ai API rate limits with backoff and request optimization. Use when encountering 429 errors, implementing retry logic, or optimizing API request throughput. Trigger with phrases like "vastai rate limit", "vastai throttling", "vastai 429", "vastai retry", "vastai backoff".
twinmind-rate-limits
Implement TwinMind rate limiting, backoff, and optimization patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for TwinMind. Trigger with phrases like "twinmind rate limit", "twinmind throttling", "twinmind 429", "twinmind retry", "twinmind backoff".
together-rate-limits
Together AI rate limits for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together rate limits".
techsmith-rate-limits
TechSmith rate limits for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith rate limits".
supabase-rate-limits
Manage Supabase rate limits and quotas across all plan tiers. Use when hitting 429 errors, configuring connection pooling, optimizing API throughput, or understanding tier-specific quotas for Auth, Storage, Realtime, and Edge Functions. Trigger: "supabase rate limit", "supabase 429", "supabase throttle", "supabase quota", "supabase connection pool", "supabase too many requests".
stackblitz-rate-limits
WebContainer resource limits: memory, CPU, file system size, process count. Use when working with WebContainers or StackBlitz SDK. Trigger: "webcontainer limits".