ACRCloud · Rate Limits

Acrcloud Rate Limits

ACRCloud meters the Identification API per recognition request and applies per-project concurrency limits tied to the plan provisioned for each access key. The Console and Metadata APIs are bearer-token administrative APIs with their own per-account request limits. Specific per-plan request-per-second and monthly recognition quotas are configured per project and are not reconciled in this artifact.

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

It captures 5 rate-limit definitions, measuring concurrent_requests, requests, bytes, and platforms.

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

Tagged areas include Audio, Music Recognition, Audio Fingerprinting, Broadcast Monitoring, and Metadata.

5 Limits Throttle: 429
AudioMusic RecognitionAudio FingerprintingBroadcast MonitoringMetadataRate LimitingQuotasThrottling

Limits

Identification Concurrency project
concurrent_requests
see provider documentation
Concurrent recognition requests per project/access key, provisioned by plan.
Recognition Quota project
requests
see provider documentation
Monthly recognition allowance, varies by plan and product.
Sample Size request
bytes
5MB
Identification API sample/fingerprint payload must be under 5MB; samples under 15s are recommended.
Console API Requests account
requests
see provider documentation
Per-account request limits on the bearer-token Console API.
Metadata Platforms Per Request request
platforms
5
External Metadata API allows a maximum of 5 platforms per request.

Policies

Per-Plan Provisioning
Concurrency and recognition quotas scale with the plan provisioned for each project/access key.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After where present.

Sources