ScrapeCreators and Bright Data Web Scraper API offer pay-as-you-go social media scraping without a required monthly subscription. Choose ScrapeCreators for non-expiring credits across supported public social endpoints. Choose Bright Data’s pay-as-you-go option if you prefer a delivered-record billing unit. Its wallet and monthly free allowance work differently from a forever credit pack.
I run ScrapeCreators. That’s my bias, so I’ve put the purchase terms and catches next to the recommendations. I checked the providers’ own pages on October 28, 2026. This is a billing comparison, not a cross-provider reliability benchmark.
Quick comparison
| API | Smallest published paid entry | What gets metered | Unused balance | Main reason to choose it |
|---|---|---|---|---|
| ScrapeCreators | $47 for 25,000 credits; 100 free signup credits | Usually a request or page; special endpoints can cost more | Purchased credits never expire | Public social-data jobs that stop and start |
| Bright Data Web Scraper API | $1.50 per 1,000 records on PAYG; fund a wallet after the free allowance | Delivered records, with an incorrect-input billing exception | Free allowance resets monthly; paid-wallet lifetime not established here | Record-based budgeting and bulk delivery |
Bright Data’s free-tier docs say PAYG has no minimum commitment. They do not specify a numeric minimum deposit. Check the funding screen before treating the per-record rate as your smallest possible payment.
Prepaid requests and metered records are different
If you want to buy credits, leave the project alone for a few months, then return, an explicit non-expiry promise matters. ScrapeCreators publishes one.
But a request credit is not a post. A request can return a page containing several posts, and retrieving another page consumes another request. ScrapeCreators’ TikTok feed docs price successful pages at one credit, including empty results.
Bright Data meters delivered records. A discovery job can produce many records from one submission. Comparing its per-record price with a competitor’s per-request price tells you little until you know the output you need.
For arbitrary websites, use the separate pay-as-you-go scraping guide. This list is for supported public social data, not general crawling.
1. ScrapeCreators for non-expiring social API credits
ScrapeCreators’ docs cover public social profiles, posts, videos, comments, and other platform-specific data. It is a fit when you already know the social resource or supported discovery endpoint your application needs.
The current packs are $47 for 25,000 credits and $497 for 500,000. At one credit per request, that’s $1.88 and $0.994 per 1,000 requests. Those are allocated unit costs, not a promise that every endpoint costs one credit. For example, Find Social Profiles costs 10 credits per live request.
New accounts start with 100 free credits, without a card. The homepage also lists optional bonus-credit tasks. Those are separate from the automatic signup grant.
Two billing details are easy to miss:
- An empty successful page can still cost a credit. TikTok Comments is an explicit exception: pages with comments cost one credit; empty pages cost zero.
- Supported cache hits cost zero credits only when an acceptable cached response exists. A miss runs a live scrape at the endpoint’s normal price. Accepting older data is a freshness choice, not guaranteed free collection.
The limit: ScrapeCreators is not an arbitrary-URL scraper. Endpoint coverage and response fields vary. Inspect the specific endpoint instead of expecting every platform to return the same schema or every public post to appear in a feed.
2. Bright Data for record-metered social collection
Bright Data’s social scraper catalog includes Instagram profiles and posts, TikTok profiles and comments, YouTube videos, Facebook posts, and other public social collections. Its FAQ distinguishes collecting known URLs from discovering records through search inputs.
The published PAYG rate is $1.50 per 1,000 records. Select PAYG, not its separate monthly Scale plan, if avoiding a subscription is the requirement.
There is still a prepaid wallet. The free-tier docs describe 5,000 monthly free credits shared across eligible products. For Web Scraper API, one credit covers one record. Unused free credits do not roll over. Afterward, usage draws from deposited funds; without funds, requests stop. This is not a published forever-pack promise for the paid wallet.
The billing caveat deserves more attention than the headline. The pricing page says failed deliveries are not charged, but the Scraper API FAQ says records that fail because the input was incorrect are still billed. Validate inputs before submitting a batch.
Choose Bright Data when record-based metering and bulk collection fit your pipeline. Expect to handle scraper-specific inputs, asynchronous jobs, and result delivery. Submitting a job is not the same as receiving usable records.
Budget the polling before buying credits
A monitoring job’s cost depends on how often you repeat it. Start with:
Billable requests = targets × checks per day × days × pages per check, plus paid retries and enrichment calls.
Here is an illustrative ScrapeCreators budget using the verified $47 pack. Assume one one-credit profile request per target per check, no cache hits, no free credits, and no extra pages:
| Hypothetical schedule | Requests over 30 days | Credits | Allocated cost at $47 / 25,000 credits |
|---|---|---|---|
| Check 100 profiles once daily | 3,000 | 3,000 | $5.64 |
| Check 100 profiles hourly | 72,000 | 72,000 | $135.36 |
These are calculations, not observed workloads or monthly plans. The first schedule still requires a $47 purchase after trial credits; it does not create a $5.64 checkout option. The hourly schedule exceeds one entry pack. Buying a larger pack changes the unit rate and upfront payment.
For feed monitoring, add the actual pages fetched. For Bright Data, model billable records rather than translating this request table directly into its price. Repeated observations of the same profile are separate collection work, even if you later deduplicate them.
Before scheduling anything, cap pages per run, retry attempts, and daily spend. Decide whether every profile needs hourly checks or whether a daily snapshot answers the question.
Public inputs do not unlock private metrics
Both options here target public collection, as described in the ScrapeCreators introduction and Bright Data social product page.
A public profile URL does not grant access to its owner’s private analytics. Do not sell public view counts as watch time, or ad-library entries as a competitor’s complete spend and conversions. If those private metrics are required, this shortlist does not solve the job.
Define the required fields before choosing a provider. Treat missing or null counts as unknown, not zero. A supported platform name alone does not establish access to every profile, date range, or metric.
Check usable results, not just HTTP 200
For your trial, pick public inputs that resemble the production workload. Include a profile, a known post, and a paginated collection if your product needs all three. Then check:
- Does the returned ID and author match the input?
- Are the required fields present and in the expected types?
- Is the observation fresh enough, including any cache timestamp?
- Does pagination return new IDs, and does the cursor advance?
- What did the account actually charge for valid, empty, and failed responses?
Track billed units alongside rows accepted by your application. Calculate cost per usable result = allocated collection spend ÷ accepted results. Keep the upfront cash payment separate when prepaid credits remain unused.
ScrapeCreators’ response-contract notes document some billable HTTP-200 placeholders alongside uncharged restricted-resource responses. Neither HTTP status nor a success flag alone proves you received the data your application needs.
Which one would I pick?
I’d start with ScrapeCreators for a supported public social workflow that needs non-expiring credits. I’d choose Bright Data when delivered-record metering and bulk delivery better match the job.
If you’re replacing an Actor-based workflow, the Apify vs ScrapeCreators comparison covers that separate decision. For this one, choose the billing unit and public-data contract before buying the biggest pack. You can start ScrapeCreators with the free credits.
Frequently asked questions
Which credits never expire?
ScrapeCreators explicitly publishes non-expiring purchased credits. Bright Data’s free allowance resets monthly; do not treat that allowance or its funded wallet as the same offer.
Does one credit buy one post?
Usually not. Request-priced APIs can return multiple posts on a page, and another page costs another request. Special endpoints can consume more credits. Bright Data Web Scraper API uses a different, per-record meter.
Can these APIs return a competitor’s watch time or ad spend?
Public collection does not grant access to private watch time or a competitor’s Ads Manager. Public views and ad-library entries are not substitutes for those private metrics.
Is no subscription the same as no recurring payment?
Check the account settings. A manually funded wallet and an enabled automatic top-up behave differently. Bright Data documents optional auto-recharge; you do not need a monthly plan to spend money repeatedly.
Sources checked
Pricing and billing sources were checked on October 28, 2026. The linked pages above are provider-owned pricing, documentation, and terms. The polling table is a calculated example, not a benchmark. No cross-provider success-rate, speed, or completeness ranking is claimed.
