Agent skill · software engineering · jeremylongshore
fondo-rate-limits
Manage rate limits for Fondo-connected services including Gusto API,
Why this skill is useful
Adds executable scripts for managing API rate limits across multiple financial services, which are not commonly found in public documentation.
What it needs
Requires typescript installed locally. Requires gusto, mercury, plaid, quickbooks, stripe account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fondo Rate Limits Prerequisites Confirmed provider limits, an approved concurrency/retry policy, opaque queue telemetry, a finance owner, and synthetic test workload. Instructions Honor throttle signals, use bounded backoff and idempotency, route exhausted work to reviewed handling, and reduce load before resuming. Output Publish a rate-control receipt with policy version, aggregate throttles, queue outcome, owner, and manual disposition—never financial payloads or credentials. Examples Simulate a throttle for a fictional export, verify the retry runs once under its operation ID, and send repeated failure to review without exposing records. Overview Fondo itself is a managed tax and accounting service without direct API rate limits, but startups building parallel integrations to the same financial providers Fondo connects to (Gusto, QuickBooks, Plaid, Stripe, Mercury) must coordinate their own API calls to avoid shared-limit conflicts. During Fondo's nightly sync windows, your direct API calls compete for the same provider quotas, making careful scheduling and throttling critical for tax-season workloads and month-end reconciliation batches. Rate Limit Reference Endpoint / Provider Limit Window Scope --------------------- ------- -------- ------- Gusto payroll API 50 req 1 minute Per access token QuickBooks Online API 500 req, 10 concurrent 1 minute Per realm (company) Plaid transactions 100 req 1 minute Per clientid Stripe reads 100 req/sec 1 second Per API key Mercury banking API 50 req 1 minute Per API key Rate Limiter Implementation Retry Strategy Batch Processing Error Handling Issue Cause Fix ------- ------- ----- Gusto 429 during payroll sync Fondo nightly sync competing Schedule calls outside midnight UTC window QuickBooks concurrent limit 10+ parallel requests Cap concurrency at 8 with p-queue Plaid ITEMLOGINREQUIRED Token expired mid-batch Re-authenticate, resume from last offset Stripe idempotency conflict Duplicate key on retry Use unique idempotency key …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fondo-rate-limits