Skip to main content

Documentation Index

Fetch the complete documentation index at: https://aura-4ecab767.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

The Aura API enforces per-minute rate limits on every request.

​
Tiers

TierReads (req/min)Writes (req/min)
Anonymous60 per IP10 per IP
API key600 per key60 per key
Custom per-key limits can be set in the api_keys.rate_limit_per_min column of the database — useful for partner integrations that need higher headroom.

​
Response headers

Every response carries the standard IETF draft-ietf-httpapi-ratelimit-headers set: 
RateLimit-Limit: 600
RateLimit-Remaining: 547
RateLimit-Reset: 38
HeaderMeaning
RateLimit-LimitTotal requests allowed in the current window.
RateLimit-RemainingRequests remaining in the current window.
RateLimit-ResetSeconds until the window resets.

​
Hitting the limit

When you exceed your budget, the API returns 429 Too Many Requests: 
{
  "statusCode": 429,
  "code": "RATE_LIMITED",
  "message": "Rate limit exceeded. Try again in 38s."
}
The same RateLimit-* headers are returned on the 429 response so your client can back off precisely.
If you anticipate sustained throughput above the per-key limit (e.g. high-frequency market makers), reach out on Telegram and we’ll provision a higher-budget partner key.