From fondo-pack
Documents rate limits and queuing strategies for Gusto, QuickBooks, Plaid, Stripe APIs alongside Fondo integrations. Includes limits table and TypeScript PQueue example.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fondo-pack:fondo-rate-limitsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fondo itself has no API rate limits (it's a managed service). But if you build parallel integrations to the same providers Fondo uses (Gusto, QuickBooks, Plaid, Stripe), you share rate limits.
Fondo itself has no API rate limits (it's a managed service). But if you build parallel integrations to the same providers Fondo uses (Gusto, QuickBooks, Plaid, Stripe), you share rate limits.
| Provider | Rate Limit | Scope |
|---|---|---|
| Gusto API | 50 requests/min | Per access token |
| QuickBooks Online | 500 requests/min, 10 concurrent | Per realm |
| Plaid | 100 requests/min | Per client_id |
| Stripe | 100 reads/sec, 200 writes/sec | Per API key |
| Mercury API | 50 requests/min | Per API key |
// If you also call Gusto API directly, coordinate with Fondo's sync schedule
// Fondo typically syncs payroll data daily at midnight UTC
// Schedule your own Gusto API calls outside this window
import PQueue from 'p-queue';
const gustoQueue = new PQueue({
concurrency: 2,
interval: 60_000,
intervalCap: 40, // Stay under 50/min to leave room for Fondo
});
For security, see fondo-security-basics.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skills --plugin fondo-packSets up Fondo account and configures integrations with Gusto, QuickBooks, Plaid banks, and expense tools like Brex for automated bookkeeping and R&D tax credits. Triggers: 'setup fondo'.
Implements exponential backoff with jitter, retries, and queuing for Fireflies.ai GraphQL API rate limits. Handles 429 errors and too_many_requests for optimized throughput.
Implements Clerk Backend API rate limit handling with TypeScript retry logic, batching, and header monitoring. Use when hitting 429 errors or scaling API usage.