RandomAPI

HomePricingDocumentationBlogLoginSign Up

Choose from our 3 simple plans

Free
$0.00
  • 500 daily results
  • 10 results / request
  • 256 KB list data
  • 1 API
  • 5 snippets
  • X ads disabled
  • X Offline APIs
  • 1 Generator 1
  • 60/120/5 Cache settings 2
Standard
$5.00
  • 100,000 daily results
  • 500 results / request
  • 5 MB list data
  • 10 APIs
  • 25 snippets
  • ads disabled
  • X Offline APIs
  • 3 Generators 1
  • 120/240/10 Cache settings 2
Premium
$10.00
  • unlimited daily results
  • 2,500 results / request
  • 25 MB list data
  • unlimited APIs
  • unlimited snippets
  • ads disabled
  • Offline APIs
  • 5 Generators 1
  • 240/480/20 Cache settings 2
Here be techno jargon
1: API requests are queued into the generator with the least number of tasks. If there are many users of a tier currently using a generator, it may take a longer time for your results to be generated. Example: 100 tasks spread out over 5 generators gives each generator a load of 20 tasks while 100 tasks all in 1 generator would be significantly slower to receive results for since only 1 generator is doing all of the work. tl;dr: bigger numbers are better.

2: If your API uses Lists/Snippets, their contents are cached in memory in order to speed up access times. 60/120/5 means 60 seconds TTL in local cache, 120 seconds TTL in redis cache, and the Generator has 5 MB of local cache. When you make your intial API request, it has to read in all of the List/Snippet data into memory from disk. This is a timely process, so caching solves this problem by making your list data available in memory until the list hasn't been accessed for X seconds. At that point, your list/snippet will be removed from the local cache and any request after that will either have to check the redis cache, or worst case, reread the data from disk again. tl;dr: bigger numbers are better.