Skip to main content

Rate Limit Overview

To ensure platform stability and fair usage, Memories.ai API enforces rate limits based on the type of API endpoint you are calling.
Rate limits are applied per account. All API keys under the same account share the same rate limit quota.

Rate Limit Tiers

Standard APIs

1 QPS (Query Per Second)Applies to most API endpoints including:
  • Video / Audio / Image Upload
  • Transcription
  • Embeddings Generation

Scraping & Task APIs

Varies by endpoint and channelApplies to scraping and long-running task endpoints including:
  • YouTube / TikTok / Instagram / Twitter Scraping
  • Async task-based processing

Understanding Models

Model Provider Rate LimitRate limits follow the underlying model provider’s own limits:
  • Video Understanding Models (VLM)
  • Image Understanding Models (ILM)

Stream Processing

Concurrent Stream LimitLimited by max concurrent streams per account (video + audio combined)

Detailed Rate Limits by Endpoint

Video Processing — 1 QPS

Audio to Text — 1 QPS

Video & Image Understanding — 1 QPS

Embeddings — 1 QPS

Stream Processing — Concurrent Stream Limit

Access Required: Stream processing features are not enabled by default. Please contact sales to enable stream processing for your account.
Stream processing endpoints are limited by the maximum number of concurrent streams per account (video + audio combined), rather than QPS.
When the server capacity is reached, the API returns status code 16 (Capacity Reached). Please retry later or contact sales for a higher concurrent stream limit.

Social Media Scraping

Rate limits for scraping endpoints vary by endpoint type and the channel parameter used.

Metadata & Transcript Endpoints

These endpoints accept a channel parameter (rapid / memories.ai / apify). Rate limits are enforced per channel.

Detail & Comment Endpoints

These endpoints do not use a channel parameter.

Video Understanding Models — Model Provider Rate Limit

Memories.ai does not impose its own QPS limit on these endpoints. The effective rate limit is determined by the underlying model provider (e.g., Google Gemini, Amazon Nova, Alibaba Qwen). If you exceed the provider’s throughput limit, the API will return an error. Usage is also subject to your account’s token quota and billing limits.
If you are choosing between providers, see Video Model Selection or Image Model Selection before optimizing for rate limits alone.

Image Understanding Models — Model Provider Rate Limit

What Happens When You Exceed the Limit?

If you exceed the rate limit, the API will return a 429 Too Many Requests response:
Recommended retry strategy: Implement exponential backoff starting with a 1-second delay, doubling each retry, up to a maximum of 32 seconds.
Repeated rate limit violations may result in temporary suspension of your API key. Please ensure your application respects the rate limits.

Need Higher Rate Limits?

If your use case requires higher throughput, we offer customized rate limit plans for enterprise customers.

Contact Sales

Get in touch with our sales team to discuss a custom rate limit plan tailored to your needs.
Enterprise plans can include increased QPS/QPM limits, dedicated infrastructure, and priority support.