Search the Telegram, TikTok and X catalog

Discovery search over our own directory: filter by audience size, language, category and free text, plus X-only quality filters for account age, follower ratio and posting activity. Reads the catalog we already crawl, so it costs nothing upstream.

This is a catalog read: it is served from the CRM Solid database in milliseconds, costs one budget unit, and reports how old the reading is in meta.cache_age_s. It needs the tools:use scope (Tools): Run the analysis tools: valuation, follower audit, scoring, and more.

curl "https://crmsolid.com/data-api/v2/tools/audience-finder?platform=x" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/tools/audience-finder?platform=x", {
  headers: {
    Authorization: `Bearer ${process.env.CRM_SOLID_DATA_API_KEY}`,
  },
});

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 os

import requests

res = requests.get(
    "https://crmsolid.com/data-api/v2/tools/audience-finder?platform=x",
    headers={"Authorization": f"Bearer {os.environ['CRM_SOLID_DATA_API_KEY']}"},
    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.

Platform

x

Rows

1 items

Page

1

Has more

yes

{
  "data": {
    "platform": "x",
    "rows": [
      {
        "id": "44196397",
        "handle": "cz_binance",
        "name": "CZ",
        "bio": "Ex-Binance. Building. [email hidden]",
        "audience": 9124800,
        "language": "en",
        "category": "crypto",
        "verified": true,
        "avatar_url": "https://pbs.twimg.com/profile_images/1739231242/cz.jpg",
        "profile_url": "https://x.com/cz_binance",
        "weekly_growth": 18402,
        "tier": "S",
        "last_seen": "2026-08-22T04:10:33.000Z",
        "avg_views": null,
        "posts_per_day": null,
        "total_likes": null,
        "video_count": null,
        "bio_link": null,
        "post_count": 41208,
        "account_created_at": "2009-06-02T20:12:29.000Z",
        "location": "Dubai"
      }
    ],
    "page": 1,
    "has_more": true
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42
  }
}

• 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.

This call only draws on the ordinary per-minute and per-day columns. Every response reports where you stand in X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and the X-Plan headers.

• GET/toolsList every analysis tool
• POST/tools/valuationValue an X account
• POST/tools/shadowban-checkCheck an X account for visibility filtering
• POST/tools/follower-auditAudit an X account's followers for fakes
• POST/tools/engagement-calculatorMeasure an X account's engagement rate
• POST/tools/best-posting-timeFind when an X account should post
• POST/tools/algorithm-scoreScore an X account against the ranking signals
• POST/tools/tweet-analyzerAnalyze a single X post
• POST/tools/mention-checkerSee who is mentioning an X account
• POST/tools/growth-simulatorProject how long a follower target takes
• GET/tools/profile-picFetch an X profile picture URL
• POST/tools/instagram/engagementMeasure an Instagram account's engagement
• POST/tools/instagram/moneyEstimate Instagram sponsorship earnings
• POST/tools/tiktok/engagementMeasure a TikTok account's engagement
• POST/tools/tiktok/moneyEstimate TikTok brand-deal earnings
• POST/tools/youtube/moneyEstimate YouTube ad earnings
• POST/tools/youtube/channel-valueEstimate what a YouTube channel is worth

Reference path: /data-api/reference/tools-audience-finder