Agent skill · software engineering · jeremylongshore
ramp-rate-limits
Implement a shared Ramp request budget with rolling-window throttling, bounded retries, pagination, and 504 recovery. Use when clients receive 429 or 504 responses or share one outbound IP. Trigger with "Ramp rate limit" or "Ramp 429".
Why this skill is useful
Provides specific API integration patterns and error handling for Ramp's corporate card management that the AI wouldn't reliably generate on its own.
What it needs
Requires ramp account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ramp Rate-Limit and Timeout Control Overview Coordinate all workers that share an egress IP, because independent per-process retries can amplify a rolling-window breach. Preserve idempotency and reconcile ambiguous writes before retry. Prerequisites Identify the Ramp application, environment, business entities, affected data and workflows, accountable owner, and rollback boundary. Read references/official-docs.md and re-check endpoint schemas, scopes, limits, and support status before a live operation. Use synthetic fixtures or Ramp sandbox until production access and business effects are explicitly approved. Prepare approved secret storage and a sanitized evidence location. Current Contract Ramp currently documents a default limit of 200 requests per rolling 10-second window per source IP. A 429 means pause and back off; immediate retries worsen contention. Requests taking longer than 60 seconds terminate with 504, so large reads should be paginated and work units reduced. Ramp recommends exponential backoff; actual throughput is lower than theoretical throughput and endpoint constraints still apply. Instructions 1. Inventory all services, jobs, tenants, endpoints, and retry layers sharing each source IP; measure arrival rate, burst, latency, 429/504, and business priority. 2. Implement one shared rolling-window limiter below the documented ceiling, with reserved capacity for interactive or recovery traffic. 3. Use bounded exponential backoff with full jitter for 429, 5xx, and safe 504 cases; cap attempts and total elapsed time. 4. Retry reads freely within budget, but retry writes only with an endpoint-supported idempotency key and post-timeout reconciliation. 5. Reduce pages or query scope for 504s, canary concurrency changes, and request a vendor increase only with measured demand and completeness evidence. Tool Discipline Use Glob to locate candidate code, manifests, fixtures, and evidence without widening scope. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ramp-rate-limits--bf56fc