Credits

What a call costsCopy Anchor Link

• A successful call (any 2xx) costs one credit, whether it was fetched live or came from the cache.
• An error costs nothing, whatever its status.
• A list endpoint costs one credit per page: ten pages of posts are ten credits.

Credits belong to a workspace: its keys spend them, and its members share them. A new account's first workspace gets 100 free credits; a workspace made later starts with none. More come in packs under Billing in the dashboard, bought by the workspace's owner or an admin; credits never expire, and a bigger pack also lets more people join the workspace. See Pricing.

Your balanceCopy Anchor Link

Each successful call answers with an X-Credits-Remaining header: the workspace's balance after that call. The dashboard's Billing page shows the balance and every purchase, and Usage shows the calls of each key.

Running outCopy Anchor Link

At zero, calls answer 402 INSUFFICIENT_CREDITS without fetching anything. Calls already running when the balance reaches zero still finish and are charged, so it can dip a little below zero; your next purchase covers that first.

Rate limitsCopy Anchor Link

Calls are limited per workspace, across all its keys: 10 a minute until the workspace's first purchase, and 60 a minute after. Every call with a valid key counts, failed ones too. Over the limit, calls answer 429 RATE_LIMITED with a Retry-After header: the seconds until the limit lets calls through again.

Planning a batchCopy Anchor Link

• Count pages, not items. A job that reads 50 subreddits, 3 pages each, costs 150 credits.
• Pace it. At 60 calls a minute, 1,000 calls take about 17 minutes. Run a few calls at a time, and wait out Retry-After when it comes.
• Keep your own copies. The same call within a few minutes comes from the cache (meta.cached is true), and it still costs a credit.
• Watch the balance. Read X-Credits-Remaining as you go, and stop or buy more before it reaches zero.