Credit Management

The Streamforge External API prices every call in credits. Understanding how credits work helps you plan your API consumption. Each call is charged once, at its endpoint’s tier, whatever the number of IDs it names or results it returns. A bulk call for 25 profiles costs 0.01 credit, the same as a call for one profile.

​

Credit Costs

​

Credits by endpoint

Creator search, brand, industry, rate and creator request endpoints are available with a Streamforge API key only, not through RapidAPI.

​

Items per call

A call names or returns at most 25 items:

• Bulk calls take at most 25 IDs in profile_ids, content_ids, game_ids or handles. More returns a 400 validation error.
• List calls return at most 25 items per page. A larger limit is lowered to 25.

​

Examples

​

Credit Headers

Responses carry three headers that show your credit use: These headers are in credits. A profile request shows X-Credits-request-cost: 0.01, and so does a bulk call for 25 profiles. An email lookup shows 0.1, a brand profile 0.1 and an analysis 1. meta.credits_charged on a creator request is in credits too: 1 once the request is accepted.

​

Optimizing Credit Usage

​

Use Bulk Operations

A bulk call costs the same as a single-item call. Fetching 25 profiles in one bulk call costs 0.01 credit; fetching them one by one costs 0.25.

​

Use Full Pages

A list page costs the same whatever its limit. When you will read a whole list, use limit=25 and make fewer calls. Search endpoints cost the same whatever the limit, so ask for as many results as you will show.

​

Cache Expensive Operations

The /analysis and /audience endpoints cost 1 credit each, 100 times a profile. This data is regenerated infrequently (typically monthly), so cache results aggressively.

​

When you exceed a credit limit

The API returns 403 Forbidden

​

Credit Budget Planning

​

Best Practices

• Use bulk endpoints: Always prefer bulk operations for multiple items, up to 25 per call
• Cache expensive requests: Cache /analysis and /audience responses for extended periods
• Use full pages: A page costs the same at any limit, so use limit=25 when you read a whole list
• Monitor headers: Use headers to understand usage
• Distribute load: Stagger requests to avoid credit spikes