Credits & pricing

SocialRouter uses a pay-as-you-go credit system. No subscriptions, no minimums.

How credits work

Credits are denominated in USD
You are charged per record returned, not per request
The price is a property of the offer that served the run, and two offers of the same service can have different prices
The price you see on GET /v1/services is the price you pay, with no hidden multipliers

Pricing

The authoritative source is the live catalogue:

curl https://api.socialrouter.io/v1/services/reddit/subreddit.posts

{
  "platform": "reddit",
  "service": "subreddit.posts",
  "offers": [
    { "offer": "apify/harshmaur", "source": "apify", "price_per_record": 0.00276, "max_inputs": 10 },
    { "offer": "apify/trudax",    "source": "apify", "price_per_record": 0.00552, "max_inputs": 10 }
  ]
}

Offers are listed in failover order, cheapest first unless a rank says otherwise. The browsable comparison lives at socialrouter.io/services.

Cost calculation

cost = price_per_record × number_of_records_returned

At $0.00276 per record, 100 records cost 0.00276 × 100 = $0.276. Billing is a hold-then-capture. Before the run, an estimate based on limit and the head of the chain is held against your balance. After it, the actual cost is captured at the serving offer’s price and the difference is released. When failover switched offers, you pay that offer’s price, and earlier failed attempts are never charged.

Tracking usage

Use the usage endpoint to monitor spending:

Total credits consumed over a period
Breakdown by offer (by_provider, keyed by offer id such as apify/harshmaur) and by platform
Per-API-key spending, via key credit limits

Getting credits

Top up your account from the dashboard.

Getting started

Concepts

Best practices

How credits work

Pricing

Cost calculation

Tracking usage

Getting credits

​How credits work

​Pricing

​Cost calculation

​Tracking usage

​Getting credits

How credits work

Pricing

Cost calculation

Tracking usage

Getting credits