holder_overlap
Read-onlyIdempotent
Do two tokens share a holder base? (coordinated-network signal) — 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. Required inputs: a, b. Priced $0.05 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No wallet or API key required.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | Token A | |
| b | Yes | Token B |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | The result payload. Shape is service-specific; every field is documented in the tool description. | |
| service | No | The service id that answered. | |
| checkedAt | No | ISO-8601 timestamp of when the underlying reads were taken. |