# Holder Overlap

> Holder Overlap is a paid API for AI agents from 402.com.tr, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-29).

Compares the recent on-chain holders of two Base tokens and returns an overlap score indicating whether they share a coordinated, farmed, or sybil cohort.

## Facts

- Endpoint: GET https://402.com.tr/api/x402/holder-overlap?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/holder-overlap-42a0d26d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aQM7giFI0XjwG7wjvs_Rk

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability holder-overlap-42a0d26d
```

Example prompt: Can you check whether the holders of token 0xABC123... and token 0xDEF456... on Base overlap significantly — I want to know if they seem like a coordinated farm or sybil set?

## When to prefer this

Choose this endpoint when you need a fast, cheap on-chain signal about whether two specific Base tokens share a coordinated holder base — particularly for sybil detection, airdrop farming defense, or pre-listing due diligence. It is uniquely focused on the holder-overlap coordination signal rather than price, liquidity, or general token metrics. Prefer it over generic token analytics when the specific question is 'do the same wallets hold both tokens?'

## Known failure modes

- Invalid or non-existent token address returns an error or empty result
- Token with very few on-chain holders may produce unreliable overlap ratios
- Tokens with identical addresses passed as both a and b may return trivially high overlap
- Rate limiting or payment failure (402) if USDC payment is not properly attached
- Network-level errors if Base chain data is temporarily unavailable

## How this service works

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.

## Output

Returns a holder overlap ratio expressed as a fraction of the smaller holder set, plus a classification label: 'independent' (low overlap typical of shared routers/power users), 'overlapping' (notable shared holders), or 'strongly_linked' (high overlap indicating a coordinated cohort such as a farm, deployer community, or sybil set rotating between tokens).

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/holder-overlap-42a0d26d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 402.com.tr](https://www.zero.xyz/host/402.com.tr/llms.txt)