Estimate what a YouTube channel is worth: POST /tools/youtube/channel-value

What this endpoint answers

Estimates a sale price range for a channel by blending an earnings multiple (18-36x estimated monthly profit) with a per-subscriber asset value, and grades the channel 0-100 on subscribers, views, output volume and upload consistency.

This is a live read: it goes to the platform at request time, returns cache_age_s = 0, and is metered against a separate live-per-minute bucket on top of your tier. It needs the tools:use scope (Tools): Run the analysis tools: valuation, follower audit, scoring, and more.

Good to know

Costs money: exactly one ScrapeCreators credit per call. Metered as a live call.
Returns 503 not_configured when SCRAPECREATORS_API_KEY is unset, 404 not_found for an unknown or unreachable account, and 502 upstream_error when the upstream fails.
Ignores NEXT_PUBLIC_USE_MOCK_DATA: there is no mock path for this data.
The valuation rests on est_monthly_earnings_usd, which itself rests on a mid-band RPM and an evenly-spread view history. Errors there flow straight through to the price.
This is a desk estimate for triage, not an appraisal. A real sale prices watch time, audience geography, sponsor history and channel strikes, none of which are visible here.

Parameters

This endpoint takes no path or query parameters.

Request body

handlestringrequired
YouTube @handle, UC… channel id, or channel URL. Also accepted as `channel` or `url`.

Example request body

{
  "handle": "veritasium"
}

Call it

Authenticate with a bearer token or the x-api-key header. Keys are server-to-server credentials. Never embed one in front-end code - call the API from your own backend and forward the result.

curl

curl -X POST "https://crmsolid.com/data-api/v2/tools/youtube/channel-value" \
  -H "Authorization: Bearer psk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"handle":"veritasium"}'

JavaScript

const res = await fetch("https://crmsolid.com/data-api/v2/tools/youtube/channel-value", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "handle": "veritasium"
  }),
});

if (!res.ok) {
  const { error } = await res.json();
  throw new Error(`${error.code}: ${error.message} (${error.request_id})`);
}

const { data, meta } = await res.json();

Python

import json
import os

import requests

body = json.loads("""
{
  "handle": "veritasium"
}
""")

res = requests.post(
    "https://crmsolid.com/data-api/v2/tools/youtube/channel-value",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    json=body,
    timeout=30,
)
res.raise_for_status()

payload = res.json()
data, meta = payload["data"], payload["meta"]

Keys look like psk_live_... for production keys, psk_test_... for test keys and are minted in the panel.

What comes back

Success is { data, meta }. Failure is { error: { code, message, request_id } }. The body below is the spec's own example: the values in it are illustrative readings, not live numbers.

Channel channel id: UCHnyfMqiRRG1u-2MsSQLbXA
Channel handle: veritasium
Channel name: Veritasium
Channel avatar url: https://yt3.googleusercontent.com/veritasium.jpg
Channel verified: yes
Channel country: US
Channel subscribers: 17,800,000
Channel total views: 3,140,000,000
Channel video count: 412
Channel account age days: 6,210
Channel joined date text: Joined Jul 21, 2010
Views avg views per video: 7,621,359
Views est monthly views: 15,169,082
Views est monthly earnings usd: 37,920
Valuation estimated value usd: 690,000
Valuation value low usd: 519,300
Valuation value high usd: 860,800
Valuation score: 84
Valuation rating: premium
Scores subscriber: 38
Scores view: 28
Scores activity: 12
Scores consistency: 6
Summary strengths: Mega Influencer subscriber base, High average views per video, Established channel with long history, Verified channel
Summary weaknesses: Infrequent uploads

200 POST /tools/youtube/channel-value

{
  "data": {
    "channel": {
      "channel_id": "UCHnyfMqiRRG1u-2MsSQLbXA",
      "handle": "veritasium",
      "name": "Veritasium",
      "avatar_url": "https://yt3.googleusercontent.com/veritasium.jpg",
      "verified": true,
      "country": "US",
      "subscribers": 17800000,
      "total_views": 3140000000,
      "video_count": 412,
      "account_age_days": 6210,
      "joined_date_text": "Joined Jul 21, 2010"
    },
    "views": {
      "avg_views_per_video": 7621359,
      "est_monthly_views": 15169082,
      "est_monthly_earnings_usd": 37920
    },
    "valuation": {
      "estimated_value_usd": 690000,
      "value_low_usd": 519300,
      "value_high_usd": 860800,
      "score": 84,
      "rating": "premium"
    },
    "scores": {
      "subscriber": 38,
      "view": 28,
      "activity": 12,
      "consistency": 6
    },
    "summary": {
      "strengths": [
        "Mega Influencer subscriber base",
        "High average views per video",
        "Established channel with long history",
        "Verified channel"
      ],
      "weaknesses": [
        "Infrequent uploads"
      ]
    }
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42,
    "cache_age_s": 0
  }
}

The meta block

request_idstringrequired
Unique id for this request. Quote it in a support ticket.
generated_atstringrequired
Server time the response was produced.
took_msintegerrequired
Milliseconds spent server-side.
pagePageoptional
sourcestringoptional
Which backend served the payload, for endpoints with more than one.
cache_age_sintegeroptional
Age of the underlying data in seconds. 0 for live reads.

When it fails

POST /tools/youtube/channel-value documents 7 failure statuses. Branch on error.code, which is stable and enumerated; message is prose and may change.

401Unauthorizedunauthorized | invalid_key
No key was presented, or the key is unknown, revoked or expired.
402PaymentRequiredpayment_required | subscription_inactive
The key is valid but the plan behind it cannot serve the call: the included requests are spent and overage is switched off, capped or unfunded (payment_required), or the billing period lapsed and was not renewed (subscription_inactive). Retrying does not help; paying does. The X-Plan-* headers on this response say how far past the line you are.
Carries X-Plan, X-Plan-Limit, X-Plan-Overage, X-Plan-Period-End, X-Plan-Remaining.
403Forbiddenforbidden_scope | forbidden_ip
The key is valid but not allowed to make this call: it lacks the scope, or the request came from an address outside the key's allowlist.
422InvalidRequestinvalid_request
A parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.
429RateLimitedrate_limited | quota_exceeded
Either the burst ceiling for the current minute or the daily quota is spent. Distinguish with the code: rate_limited clears within the minute, quota_exceeded does not clear until 00:00 UTC.
Carries Retry-After, X-Quota-Limit, X-Quota-Remaining, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-Request-Id.
500InternalErrorinternal_error
Something failed on our side. Internals are never leaked; quote the request id.
503Unavailableupstream_timeout | upstream_error | not_configured
The request could not be served right now. BRANCH ON error.code, not on the status: 'upstream_timeout' means a source was too slow (this is what a catalog query hitting its 15-second statement timeout returns, so it is reachable from any endpoint that reads the corpus, not only the live-scrape ones) and the same call is worth retrying with backoff - narrowing it with a smaller limit, a filtered scope or a less popular account makes it far less likely; 'upstream_error' means a source was unreachable, so back off further; 'not_configured' means the capability has no backing service in this deployment, and retrying will never help.

Every response carries X-Request-Id and meta.request_id. Quote it in support requests.

Coverage and limits

This endpoint covers YouTube. Rate limits come from the tier on your key.

YouTube

Tier	Requests a minute	Requests a day	Live reads a minute
free	30	1,000	5
standard	120	25,000	20
pro	600	250,000	60
unlimited	6,000	10,000,000	600

Live reads count against the live column as well as the ordinary one, so a burst of them runs out of the live bucket first. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

The rest of the Tools group

The analysis tools behind the public free-tool pages, callable directly: valuation, follower audit, scoring and the rest. Metered like a live call, because each run costs compute or an upstream fetch.

Other groups

Accounts Directory X People Live scrape Insights Trends Identity Graph Watch Research Leads

Start calling it

A key takes a minute to mint in the panel, no card. The reference covers authentication, the envelope, scopes, rate limits and every error code in one page.

Get a key All 127 endpoints Full reference What the Data API is

Reference path: /data-api/reference/tools-youtube-channel-value