Tools
LiveSensitiveSpends creditsValue an X account
/data-api/v2/tools/valuation- Scope
- tools:use
- Freshness
- live read
- Group
- Tools
- Platforms
- 1 of 7
What this endpoint answers
Estimates what an X account is worth in dollars. Reads the profile plus a sample of recent posts, scores followers, engagement, account age, authority, activity and profile completeness, and returns a low/expected/high range with the multiplier behind each factor.
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: this endpoint bills twitterapi.io credits per call. Metered as a live call.
- Returns 503 not_configured when TWITTERAPI_IO_KEY is unset, and 502 upstream_error when the credit pool is exhausted or the upstream fails. It never returns an empty 200.
- Ignores NEXT_PUBLIC_USE_MOCK_DATA: the X tools always read live data and have no mock path.
- The website's captcha and per-visitor daily caps do not apply here; your API key's tier limits do.
- Values are USD, not cents.
- Results are cached in-process for a short window, so two calls on the same handle within that window may return the same numbers without a second upstream charge.
Parameters
This endpoint takes no path or query parameters.
Request body
handlestringrequiredX handle. Accepts a bare name, @name, or a profile URL. Also accepted as `username`.
{
"handle": "elonmusk"
}
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 -X POST "https://crmsolid.com/data-api/v2/tools/valuation" \
-H "Authorization: Bearer psk_live_..." \
-H "Content-Type: application/json" \
-d '{"handle":"elonmusk"}'
const res = await fetch("https://crmsolid.com/data-api/v2/tools/valuation", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
"handle": "elonmusk"
}),
});
if (!res.ok) {
const { error } = await res.json();
throw new Error(`${error.code}: ${error.message} (${error.request_id})`);
}
const { data, meta } = await res.json();
import json
import os
import requests
body = json.loads("""
{
"handle": "elonmusk"
}
""")
res = requests.post(
"https://crmsolid.com/data-api/v2/tools/valuation",
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.
- Profile handle
- naval
- Profile twitter id
- 745273
- Profile name
- Naval
- Profile avatar url
- https://pbs.twimg.com/profile_images/1256841238298292232/ycqwaMI2.jpg
- Profile verified
- yes
- Profile banner url
- https://pbs.twimg.com/profile_banners/745273/1584485471
- Profile bio
- Angel Philosopher
- Profile location
- San Francisco
- Profile created at
- 2/5/2007, 6:07:40 PM
- Profile account age days
- 7,139
- Metrics followers
- 2,418,702
- Metrics following
- 2,114
- Metrics total posts
- 32,180
- Metrics total likes
- 12,844
- Metrics media count
- 1,290
- Metrics follower following ratio
- 1,144.1
- Metrics posts per day
- 4.5
- Engagement engagement rate
- 0.417
- Engagement avg likes
- 8,940
- Engagement avg retweets
- 1,216
- Engagement avg replies
- 934
- Engagement avg views
- 412,800
- Engagement posts sampled
- 20
- Valuation estimated value usd
- 48,600
- Valuation value low usd
- 36,450
- Valuation value high usd
- 65,610
- Valuation score
- 88
- Valuation rating
- exceptional
{
"data": {
"profile": {
"handle": "naval",
"twitter_id": "745273",
"name": "Naval",
"avatar_url": "https://pbs.twimg.com/profile_images/1256841238298292232/ycqwaMI2.jpg",
"verified": true,
"banner_url": "https://pbs.twimg.com/profile_banners/745273/1584485471",
"bio": "Angel Philosopher",
"location": "San Francisco",
"created_at": "2007-02-05T18:07:40.000Z",
"account_age_days": 7139
},
"metrics": {
"followers": 2418702,
"following": 2114,
"total_posts": 32180,
"total_likes": 12844,
"media_count": 1290,
"follower_following_ratio": 1144.1,
"posts_per_day": 4.5
},
"engagement": {
"engagement_rate": 0.4172,
"avg_likes": 8940,
"avg_retweets": 1216,
"avg_replies": 934,
"avg_views": 412800,
"posts_sampled": 20
},
"valuation": {
"estimated_value_usd": 48600,
"value_low_usd": 36450,
"value_high_usd": 65610,
"score": 88,
"rating": "exceptional"
},
"scores": {
"follower": 100,
"engagement": 82,
"age": 100,
"authority": 95,
"activity": 74,
"profile": 100
},
"factors": {
"base_follower_value_usd": 36000,
"engagement_multiplier": 1.25,
"age_multiplier": 1.15,
"authority_multiplier": 1.1,
"activity_multiplier": 0.95,
"profile_multiplier": 1.05
},
"summary": {
"size_category": "Mega Account",
"engagement_rating": "Good",
"strengths": [
"Very large, established audience",
"Account is over 15 years old",
"Strong follower to following ratio"
],
"weaknesses": [
"Posting cadence has slowed in the last 30 days"
]
}
},
"meta": {
"request_id": "req_9f2c41a8b3d5",
"generated_at": "2026-08-23T09:14:02.317Z",
"took_ms": 42,
"cache_age_s": 0
}
}
The meta block
request_idstringrequiredUnique id for this request. Quote it in a support ticket.
generated_atstringrequiredServer time the response was produced.
took_msintegerrequiredMilliseconds spent server-side.
pagePageoptionalsourcestringoptionalWhich backend served the payload, for endpoints with more than one.
cache_age_sintegeroptionalAge of the underlying data in seconds. 0 for live reads.
When it fails
POST /tools/valuation documents 7 failure statuses. Branch on error.code, which is stable and enumerated; message is prose and may change.
- 401Unauthorized
unauthorized | invalid_keyNo key was presented, or the key is unknown, revoked or expired.
- 402PaymentRequired
payment_required | subscription_inactiveThe 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.
- 403Forbidden
forbidden_scope | forbidden_ipThe 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.
- 422InvalidRequest
invalid_requestA parameter is malformed, out of range or mutually exclusive with another. `details` names the offending fields.
- 429RateLimited
rate_limited | quota_exceededEither 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.
- 500InternalError
internal_errorSomething failed on our side. Internals are never leaked; quote the request id.
- 503Unavailable
upstream_timeout | upstream_error | not_configuredThe 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 X. Rate limits come from the tier on your key.
| 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.
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.
Reference path: /data-api/reference/tools-valuation