Limits & Quotas

Payaion enforces limits to ensure fair usage and service stability. These limits apply to all users, whether using the web interface or the Aion API.

Starting conservative: storage and file caps are deliberately modest for launch and will rise as we gather usage data. Payments and storage both run on production networks — USDC on Base mainnet, blobs on Walrus mainnet.

File & storage limits

PlanPer fileTotal storageStored filesFile lifetime
No account (guest)100 MB24 hours
Basic500 MB2 GB20030 days
Pro1 GB20 GB2,000While the subscription stays active

An oversized file returns 413 size_limit_exceeded, a full account returns 403 storage_limit_exceeded, and too many stored files returns 403 file_count_limit_exceeded — all are rejected before the upload body is read, so there is nothing to retry until you free space or upgrade. See Plans & pricing for what Pro changes.

Upload rate limits

Rate limits protect the service from abuse. If you exceed a limit, you'll receive a 429 response with a Retry-After header.

ScopeUploadStatusDownload URL
Per API key5 / min30 / min30 / min
Per account10 / min60 / min60 / min
Per IP address20 / min60 / min60 / min

Concurrency limits

Concurrency limits control how many uploads can be in-flight at the same time. If you exceed the limit, you'll receive a 503 response.

ScopeMax concurrent uploads
Per API key2
Per account3
Global60

Blocked file types

The following MIME types are blocked and will return 415 Unsupported Media Type:

  • Executables (.exe, .msi)
  • Shell scripts (.sh, .bat)
  • Other executable formats (.com, portable executables)

Handling rate limits

Best practice: Check the Retry-After header in 429 and 503 responses. Wait the specified number of seconds before retrying.

Need more details?

See Errors & retries for a full list of error responses and how to handle them.