Argil · Rate Limits

Argil Rate Limits

Argil's practical throughput ceiling is the account's monthly credit balance: video generation consumes credits (roughly 1,600 credits per 25 minutes of video), so the number of renders per month is bounded by the subscription tier. The API also enforces per-key request throttling and per-request constraints - moments are limited to a 500-character transcript or ~40 seconds of audio, extras are capped at 10 key-value pairs, and render callbacks must be HTTPS. Specific per-second/per-minute request ceilings are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring credits, requests, characters, seconds, and key_value_pairs.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, Video Generation, Avatars, Rate Limiting, and Quotas.

5 Limits Throttle: 429
AIVideo GenerationAvatarsRate LimitingQuotasThrottling

Limits

Monthly Credit Quota account
credits
per subscription tier (e.g. 1,600 Classic / 6,000 Pro / 18,000 Scale)
Credits are consumed per generated video; ~1,600 credits ~= 25 minutes.
API Request Rate api_key
requests
see provider documentation
Per-key request throttling; exceeding it returns HTTP 429.
Transcript Length Per Moment request
characters
500
Each moment transcript is capped at 500 characters.
Audio Length Per Moment request
seconds
40
Each moment audioUrl clip is limited to roughly 40 seconds.
Extras Per Video request
key_value_pairs
10
Custom metadata capped at 10 key-value pairs (256 chars each).

Policies

Credit-Bounded Throughput
Generation volume is governed by the monthly credit balance; upgrade the tier or purchase credits to raise the ceiling.
Asynchronous Rendering
Rendering is asynchronous; use webhooks (VIDEO_GENERATION_SUCCESS / VIDEO_GENERATION_FAILED) instead of tight polling to stay within request limits.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/argil-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.