# Largest Reported Token Holder Share — Threshold Classification

> Largest Reported Token Holder Share — Threshold Classification is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-15).

Classifies whether the largest reported token holder's share falls within a user-defined threshold range, given token holder and circulating supply data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-bx-token-largest-holder-threshold?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/largest-reported-token-holder-share-threshold-classification-341ee7b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7mboodjHVWLkfHlWfQz_6

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 largest-reported-token-holder-share-threshold-classification-341ee7b0 -d '<json body>'
```

Example prompt: Check whether the largest token holder's share falls within the 0% to 20% threshold range — I have two observations: one where the holder has 100,000 tokens out of 1,000,000 circulating, and another where they hold 110,000 out of 1,100,000 circulating.

## When to prefer this

Choose this endpoint when you need a fast, deterministic classification of whether the largest token holder's share sits within a caller-defined threshold, using snapshot observations you already have. Ideal for compliance checks, due diligence pipelines, or automated tokenomics audits where you supply the data rather than needing a live on-chain scan. Not suitable for real-time blockchain queries or trade recommendations.

## Known failure modes

- circulating_tokens of zero or missing triggers validation error (exclusiveMinimum enforced)
- fewer than 2 row observations returns an error (minItems: 2)
- exceeding 200 rows in the array returns an error (maxItems: 200)
- holder_tokens or circulating_tokens outside allowed numeric range causes rejection
- malformed JSON input returns a bad request error

## How this service works

Largest reported token holder share — Threshold classification: Threshold classification for Largest reported token holder share. Supplied token observations only. Deterministic calculation or caller-threshold verdict, not a live scan, safety proof or trade recommendation. Specialised preset in a shared 50-profile, 20-operation engine. 0.01 USDC includes one bounded threshold classification report.

## Output

Returns a deterministic threshold classification verdict indicating whether the largest reported token holder's share (computed from supplied holder_tokens and circulating_tokens pairs) falls within the specified lower and upper bounds. The result is a bounded classification report, not a live scan or safety proof.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "holder_tokens",
     "circulating_tokens"
    ],
    "properties": {
     "holder_tokens": {
      "type": "number",
      "default": 100000,
      "maximum": 10000000000000000,
      "minimum": 0
     },
     "circulating_tokens": {
      "type": "number",
      "default": 1000000,
      "maximum": 10000000000000000,
      "minimum": 0,
      "exclusiveMinimum": 0
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "holder_tokens": 100000,
     "circulating_tokens": 1000000
    },
    {
     "holder_tokens": 110000.00000000001,
     "circulating_tokens": 1100000
    },
    {
     "holder_tokens": 100000,
     "circulating_tokens": 1000000
    },
    {
     "holder_tokens": 110000.00000000001,
     "circulating_tokens": 1100000
    }
   ],
   "maxItems": 200,
   "minItems": 2
  },
  "lower": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000000000,
   "minimum": -1000000000000000000
  },
  "upper": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000000000,
   "minimum": -1000000000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/largest-reported-token-holder-share-threshold-classification-341ee7b0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)