ReddGrow DocsCredits
How the ReddGrow credit system works
ReddGrow uses a credit system to meter API usage. Every request consumes a number of credits based on how much work the server performs. Credits reset at the start of each monthly billing period.
Credit cost tiers
| Cost | Tier | Example endpoints |
|---|---|---|
| 1 credit | Simple lookup | GET /agent/me, GET /users/{username}, GET /subreddits/{name} |
| 2 credits | List or feed | GET /subreddits/{name}/posts, GET /users/{username}/posts |
| 3 credits | Search | GET /posts/search, GET /subreddits/search, GET /posts/domain |
| 5 credits | Heavy or batch | POST /posts/batch, POST /users/batch, large paginated fetches |
The cost for a given request is always shown in the response headers (see below) so you can track consumption in real time.
Response headers
Every API response includes three credit headers:
| Header | Description |
|---|---|
X-Credits-Used | Credits consumed by this specific request |
X-Credits-Remaining | Credits left in the current billing period |
X-Credits-Limit | Total credits available on your plan |
Example headers from a search request:
X-Credits-Used: 3
X-Credits-Remaining: 487
X-Credits-Limit: 1000You can use these headers in your agent or application to implement backoff logic before the limit is reached.
Plan tiers
| Plan | Credits per month | Best for |
|---|---|---|
| Free | 50 | Evaluation and prototyping |
| Starter | 1,000 | Small projects and personal agents |
| Growth | 5,000 | Production agents with moderate traffic |
| Pro | 15,000 | High-volume applications |
| Enterprise | 100,000 | Large-scale or multi-tenant deployments |
Upgrade or change your plan at any time from Settings > Billing. Credit limits update immediately on upgrade.
Tips to reduce credit usage
Cache responses. Subreddit feeds and post data change infrequently. Cache results for 5–15 minutes to avoid redundant calls for the same data.
Use batch endpoints. If you need data for multiple users or posts, a single POST /users/batch call costs 5 credits and returns up to 50 records — far cheaper than 50 individual lookups at 1 credit each.
Paginate carefully. Fetching a large number of pages in a tight loop burns credits quickly. Fetch only as many pages as your use case requires and store results locally.
Check headers before retrying. If X-Credits-Remaining is low, add logic to pause or degrade gracefully rather than exhausting the limit mid-run.