Audience overlap between two X accounts

How much of one account's audience also follows the other, measured directly on 83M follow edges rather than inferred. Returns the shared-follower count, the share of each side, a Jaccard index, a lift against the panel base rate, and the most-followed accounts inside the shared set. This is the question an advertiser, a media buyer or an account buyer asks first, and it was not answerable through this API before.

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/overlap?a=vercel&b=nextjs" \
  -H "Authorization: Bearer psk_live_..."

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

A user id

4686835494

A username

vercel

A name

Vercel

A followers

451,669

A is verified

yes

A profile url

https://x.com/vercel

A known followers scanned

375

A known followers estimate

381

A scan truncated

no

A in panel

yes

B user id

1467726470533754880

B username

nextjs

B name

Next.js

B followers

290,945

B is verified

yes

B profile url

https://x.com/nextjs

B known followers scanned

118

B known followers estimate

119

B scan truncated

no

B in panel

yes

Overlap shared followers

67

Overlap share of a pct

17.87

Overlap share of b pct

56.78

Overlap jaccard pct

15.73

Overlap lift

717.5

Overlap exact

yes

Overlap comparable

yes

Overlap measured against

vercel

{
  "data": {
    "a": {
      "user_id": "4686835494",
      "username": "vercel",
      "name": "Vercel",
      "followers": 451669,
      "is_verified": true,
      "profile_url": "https://x.com/vercel",
      "known_followers_scanned": 375,
      "known_followers_estimate": 381,
      "scan_truncated": false,
      "in_panel": true
    },
    "b": {
      "user_id": "1467726470533754880",
      "username": "nextjs",
      "name": "Next.js",
      "followers": 290945,
      "is_verified": true,
      "profile_url": "https://x.com/nextjs",
      "known_followers_scanned": 118,
      "known_followers_estimate": 119,
      "scan_truncated": false,
      "in_panel": true
    },
    "overlap": {
      "shared_followers": 67,
      "share_of_a_pct": 17.87,
      "share_of_b_pct": 56.78,
      "jaccard_pct": 15.73,
      "lift": 717.5,
      "exact": true,
      "comparable": true,
      "not_comparable_reason": null,
      "measured_against": "vercel"
    },
    "top_shared": [
      {
        "user_id": "1010101",
        "username": "rauchg",
        "name": "Guillermo Rauch",
        "followers": 831868,
        "is_verified": true,
        "profile_url": "https://x.com/rauchg",
        "citation_score": 1460,
        "in_panel": true
      }
    ],
    "panel": {
      "size": 477868,
      "measured_at": "2026-08-31"
    }
  },
  "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.

• 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/{handle}/similarLookalike X accounts by shared audience
• 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-overlap