Api Endpoint

Holder Overlap

Do two tokens share the same recent holders — the farm / sybil / coordinated-launch signal nobody else surfaces? Reads each token's recent recipients and returns the overlap as a share of the smaller set: independent (the few % unrelated tokens share via routers/power users), overlapping, or strongly_linked (a coordinated cohort — same farm, deployer community, or a sybil set rotating between them). Pass a= and b=. A signal, not proof. Not financial advice.

Open interactive test console

Offering

Provider: 402.com.tr
Method: GET
Offering type: Api Endpoint
Transport type: http
Category: Blockchain And Crypto
Delivery: Not provided
Pricing model: Not provided
x402 version: 2

Endpoint context

URL: https://402.com.tr/api/x402/holder-overlap
MIME type: application/json
First seen: 2026-10-16T01:50:45.949Z
Last seen: 2026-11-02T21:01:35.769Z
Tags: sybil, coordinated, holder-overlap, farm, token-safety, Onchain, EVM, wallet-intel, Security, Data, holder, Base, X402

Website

Payment pricing

x402 payment terms are the authoritative price for calling this endpoint.

Payment option 1: 0.05 USDC
Atomic price: 50000 · Network: eip155:8453 · Asset: USDC · Scheme: exact

Raw x402 terms

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "50000",
    "payTo": "0x973a31858f4d2125f48c880542da11a2796f12d6"
  }
]

Observed health

Status: Healthy
Latest latency: 547 ms
Average latency: 878 ms
HTTP status: 402
Last checked: 2026-11-02T21:01:35.763Z
Reachability: 100% over 10 checks

Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.

Input schema

{
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "const": "http"
    },
    "method": {
      "type": "string",
      "enum": [
        "GET"
      ]
    },
    "queryParams": {
      "type": "object",
      "properties": {
        "a": {
          "type": "string",
          "description": "Token A"
        },
        "b": {
          "type": "string",
          "description": "Token B"
        }
      },
      "required": [
        "a",
        "b"
      ]
    },
    "pathParams": {
      "type": "object"
    }
  },
  "required": [
    "type",
    "method"
  ],
  "additionalProperties": false
}

Output schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {
    "input": {
      "additionalProperties": false,
      "properties": {
        "method": {
          "enum": [
            "GET"
          ],
          "type": "string"
        },
        "pathParams": {
          "type": "object"
        },
        "queryParams": {
          "properties": {
            "a": {
              "description": "Token A",
              "type": "string"
            },
            "b": {
              "description": "Token B",
              "type": "string"
            }
          },
          "required": [
            "a",
            "b"
          ],
          "type": "object"
        },
        "type": {
          "const": "http",
          "type": "string"
        }
      },
      "required": [
        "type",
        "method"
      ],
      "type": "object"
    },
    "output": {
      "properties": {
        "example": {
          "type": "object"
        },
        "type": {
          "type": "string"
        }
      },
      "required": [
        "type"
      ],
      "type": "object"
    }
  },
  "required": [
    "input"
  ],
  "type": "object"
}