palantir-rate-limits

Featured

Implement Palantir Foundry API rate limiting, backoff, and request queuing. Use when handling 429 errors, implementing retry logic, or optimizing API request throughput for Foundry. Trigger with phrases like "palantir rate limit", "foundry throttling", "palantir 429", "foundry retry", "palantir backoff".

AI & Automation 2,266 stars 315 forks Updated today MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Palantir Rate Limits ## Overview Handle Foundry API rate limits with exponential backoff, request queuing, and monitoring. Foundry rate limits vary by endpoint and enrollment tier. ## Prerequisites - `foundry-platform-sdk` installed - Understanding of HTTP 429 responses ## Instructions ### Step 1: Understand Foundry Rate Limits Foundry rate limits are per-user and per-endpoint. Key limits: | Endpoint Category | Typical Limit | Burst | |-------------------|---------------|-------| | Ontology reads | 100 req/s | 200 | | Ontology writes (Actions) | 50 req/s | 100 | | Dataset reads | 50 req/s | 100 | | Search queries | 20 req/s | 50 | Rate limit headers returned: - `X-RateLimit-Limit` — max requests per window - `X-RateLimit-Remaining` — requests left in window - `Retry-After` — seconds to wait (on 429) ### Step 2: Implement Retry with Backoff (Python) ```python import time import random import foundry def retry_foundry_call(fn, *args, max_retries=5, base_delay=1.0, **kwargs): """Retry Foundry API calls with jittered exponential backoff.""" for attempt in range(max_retries + 1): try: return fn(*args, **kwargs) except foundry.ApiError as e: if attempt == max_retries: raise if e.status_code not in (429, 500, 502, 503): raise # Non-retryable error delay = base_delay * (2 ** attempt) + random.uniform(0, 0.5) retry_after = getattr(e, "retry_after", None) ...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
7 months ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

figma-rate-limits

Handle Figma REST API rate limits with exponential backoff and request queuing. Use when encountering 429 errors, implementing retry logic, or optimizing API request throughput for Figma. Trigger with phrases like "figma rate limit", "figma throttling", "figma 429", "figma retry", "figma backoff".

2,266 Updated today
jeremylongshore
AI & Automation Featured

palantir-performance-tuning

Optimize Palantir Foundry API performance with caching, batching, and pagination. Use when experiencing slow API responses, optimizing transform builds, or improving request throughput for Foundry integrations. Trigger with phrases like "palantir performance", "optimize foundry", "foundry slow", "palantir caching", "foundry batch".

2,266 Updated today
jeremylongshore
AI & Automation Featured

notion-rate-limits

Manage Notion API rate limits with exponential backoff, queue-based throttling, and batch optimization. Use when hitting 429 errors, implementing retry logic, or optimizing API request throughput for Notion integrations. Trigger with "notion rate limit", "notion 429", "notion retry", "notion backoff", "notion throttling", "notion too many requests", "notion queue".

2,266 Updated today
jeremylongshore
AI & Automation Featured

fireflies-rate-limits

Implement Fireflies.ai rate limiting, backoff, and request queuing. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Fireflies.ai. Trigger with phrases like "fireflies rate limit", "fireflies throttling", "fireflies 429", "fireflies retry", "fireflies backoff".

2,266 Updated today
jeremylongshore
AI & Automation Featured

apify-rate-limits

Handle Apify API rate limits with proper backoff and request queuing. Use when hitting 429 errors, optimizing API request throughput, or implementing rate-aware client wrappers. Trigger: "apify rate limit", "apify throttling", "apify 429", "apify retry", "apify backoff", "too many requests apify".

2,266 Updated today
jeremylongshore