Lookalike X accounts by shared audience

Accounts whose audience most resembles this one, found by sampling the account's followers and reading what else they follow. Graph-neighbourhood similarity, not bio or topic matching. Ranked by lift against the panel base rate, so the answer is a real neighbourhood rather than a list of whoever is globally largest.

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 insights:read scope (Insights): Engagement rates, top posts, viral patterns, cohort benchmarks.

curl "https://crmsolid.com/data-api/v2/graph/x/vercel/similar" \
  -H "Authorization: Bearer psk_live_..."

const res = await fetch("https://crmsolid.com/data-api/v2/graph/x/vercel/similar", {
  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/graph/x/vercel/similar",
    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.

Account user id

4686835494

Account username

vercel

Account name

Vercel

Account followers

451,669

Account is verified

yes

Account profile url

https://x.com/vercel

Coverage indexed followers estimate

381

Coverage measurable

yes

Sample followers sampled

250

Sample sample cap

250

Sample truncated

yes

Sample min shared followers

4

Sample candidates considered

200

Sample candidate cap

200

Panel size

477,868

Panel measured at

2026-08-31

Similar

2 items

{
  "data": {
    "account": {
      "user_id": "4686835494",
      "username": "vercel",
      "name": "Vercel",
      "followers": 451669,
      "is_verified": true,
      "profile_url": "https://x.com/vercel"
    },
    "coverage": {
      "indexed_followers_estimate": 381,
      "measurable": true
    },
    "sample": {
      "followers_sampled": 250,
      "sample_cap": 250,
      "truncated": true,
      "min_shared_followers": 4,
      "candidates_considered": 200,
      "candidate_cap": 200
    },
    "panel": {
      "size": 477868,
      "measured_at": "2026-08-31"
    },
    "similar": [
      {
        "rank": 1,
        "account": {
          "user_id": "1467726470533754880",
          "username": "nextjs",
          "name": "Next.js",
          "followers": 290945,
          "is_verified": true,
          "profile_url": "https://x.com/nextjs",
          "citation_score": 190,
          "in_panel": true
        },
        "shared_followers": 40,
        "share_of_sample_pct": 16,
        "known_followers_estimate": 119,
        "lift": 642.5
      },
      {
        "rank": 2,
        "account": {
          "user_id": "2020202",
          "username": "tailwindcss",
          "name": "Tailwind CSS",
          "followers": 288005,
          "is_verified": true,
          "profile_url": "https://x.com/tailwindcss",
          "citation_score": 102,
          "in_panel": false
        },
        "shared_followers": 12,
        "share_of_sample_pct": 4.8,
        "known_followers_estimate": 64,
        "lift": 358.4
      }
    ]
  },
  "meta": {
    "request_id": "req_9f2c41a8b3d5",
    "generated_at": "2026-08-23T09:14:02.317Z",
    "took_ms": 42,
    "page": {
      "limit": 50,
      "next_cursor": "eyJrIjoiMTczNDU2IiwiZCI6ImEifQ",
      "count": 50
    }
  }
}

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

• 404NotFoundnot_found

  The addressed resource does not exist.

• 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/graph/x/overlapAudience overlap between two X accounts
• GET/graph/x/{handle}/notable-followersFollowers of an X account ranked by their own influence
• GET/graph/x/{handle}Follow-graph coverage for one X account

Reference path: /data-api/reference/graph-x-similar