Agent skill · software engineering · jeremylongshore
palantir-rate-limits
Analyze and design bounded Foundry API concurrency, backoff, pagination, and overload behavior from current documented limits. Use when preventing or handling HTTP 429 or 503 responses. Trigger with "Palantir rate limit".
Why this skill is useful
Adds executable scripts for handling Palantir Foundry API rate limits with backoff and request queuing that aren't in public docs.
What it needs
Requires foundry-platform-sdk installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Palantir API Limit and Concurrency Control Overview Protect Foundry and the caller from retry storms. Budget requests across the acting user, bound concurrent work, honor server responses, and distinguish retryable throttling from authorization, validation, or permanent resource errors. Prerequisites Identify the acting user or service user, applications sharing it, endpoints, workload peaks, page/batch shape, and service objective. Capture response status, request identifiers, timestamps, server timing guidance, retry count, and current concurrency. Read references/official-docs.md immediately before setting numeric budgets because effective and endpoint-specific limits may change. Prepare load tests in an approved non-production scope. Current Contract The current general API documentation lists global per-user rate and concurrency limits across Foundry API endpoints. Individual endpoints may impose stricter limits and return 429 or 503. Palantir recommends exponential backoff for throttled requests. Limits can vary in practice, and disruptive throttling may require Palantir Support rather than client-side limit evasion. Authentication Attribute the request budget to the actual OAuth principal. Do not distribute calls across extra tokens, users, or service users to evade a limit. Keep token material out of metrics and retry logs. Instructions 1. Inventory every worker and application using the same principal and estimate peak request rate plus in-flight concurrency. 2. Set a conservative shared concurrency budget and bounded queue with deadlines and cancellation. 3. Retry only documented transient statuses, honoring server guidance and using capped exponential backoff with jitter. 4. Use pagination, selective properties, batching supported by the endpoint, idempotency controls, and workload coalescing to reduce demand. 5. Load-test below the approved ceiling, simulate 429 and 503, and verify recovery without duplicate writes or unbounded backlog. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/palantir-rate-limits--8e0c17