AlphaSense · Rate Limits

Alphasense Rate Limits

AlphaSense does not publish numeric per-second or per-minute rate limits for the Agent API or Utility APIs in the public developer portal. The developer.alpha-sense.com documentation references a "Credits & Rate Limits" section that governs GenSearch and Deep Research consumption, but the credit pricing, monthly allowance, and throttling ceiling are negotiated per customer contract. Standard HTTP 4xx/5xx response codes are applied; 429 is returned on credit-pool or burst exhaustion. The /auth bearer token has a finite lifetime and must be refreshed. This artifact stays reconciled:false until paired with a real customer contract.

Alphasense Rate Limits is the machine-readable rate-limit profile for AlphaSense on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring credit, requests, documents, and token.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, unauthorized, and serverError.

Tagged areas include Market Intelligence, Search, Generative AI, Agents, and GraphQL.

4 Limits Throttle: 429
Market IntelligenceSearchGenerative AIAgentsGraphQLRate LimitingCredits

Limits

GenSearch / Deep Research Credit Pool customer
credit · month
contracted
Generative calls (GenSearch in any mode, Deep Research, Workflow Agents invoking generative steps) draw from a contracted monthly credit pool. Exhausting the pool returns 429 and requires top-up or contract uplift.
GraphQL Burst (per-customer) customer
requests · minute
contracted
Per-customer burst throttling on the shared /gql endpoint. Numeric ceiling not published; behaviour returns 429 on excessive throughput.
Ingestion Throughput customer
documents · hour
contracted
Enterprise Intelligence ingestion runs against a contracted ingestion quota; large initial loads are typically scheduled with Solutions Engineering.
Bearer Token Lifetime session
token · hour
short-lived
/auth returns a bearer token with a finite expires_in. Clients must refresh the token (or re-authenticate) before expiry.

Policies

429 Throttling
AlphaSense returns 429 on burst exhaustion or credit-pool exhaustion. Implement exponential backoff with jitter and treat persistent 429s as a signal to renegotiate the credit pool.
Token Refresh
Refresh the bearer token before expires_in elapses; do not cache indefinitely. Long-running agent workloads should hold a credential manager that re-auths against /auth.
Polling Cadence
GenSearch / Deep Research conversations are polled until progress reaches 1.0. Recommended cadence is a few seconds per poll; do not tight-loop.
Credit Accounting
Deep Research is materially more expensive in credits than fast or auto GenSearch modes. Route the right mode for the question to control burn.

Sources