Agent skill · software engineering · jeremylongshore
glean-rate-limits
Glean Indexing API: ~100 requests/min per token.
Why this skill is useful
Includes executable scripts for rate limiting and bulk document indexing that enhance API interaction capabilities.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Glean Rate Limits Overview Glean's APIs split into two tiers: the Indexing API for pushing documents into the search corpus, and the Client API for executing searches. The Indexing API handles bulk document ingestion at approximately 100 requests per minute, while search queries are capped at 60 per minute per token. Organizations indexing large knowledge bases (100K+ documents from Confluence, Notion, or internal wikis) must implement careful batching to avoid 429 responses that can stall multi-hour ingestion pipelines. Rate Limit Reference Endpoint Limit Window Scope ---------- ------- -------- ------- Indexing - single document 100 req 1 minute Per API token Indexing - bulk (100 docs/req) 20 req 1 minute Per API token Search queries 60 req 1 minute Per API token People search 30 req 1 minute Per API token Entity extraction 40 req 1 minute Per API token Rate Limiter Implementation Retry Strategy Batch Processing Error Handling Issue Cause Fix ------- ------- ----- 429 on bulk index Exceeded 20 bulk req/min Space batches 4s apart, use Retry-After 413 Payload Too Large Batch > 100 docs or > 10MB Split into smaller batches Search 429 Monitoring dashboard polling too fast Cache search results for 30s Partial index failure Some docs rejected in bulk Check response failedDocuments array, retry those 401 token expired Rotating API credentials Refresh token before long ingestion runs Prerequisites An approved per-operation budget, observed response-header baseline, and a test environment with synthetic requests. Idempotency keys for writes, a bounded queue, and a dead-letter path for exhausted retries. A defined caller identity and datasource scope so throttling cannot be bypassed by broadening credentials. Instructions 1. Classify calls as read or write, apply per-scope concurrency limits, and honor server retry guidance when it is present. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/glean-rate-limits