# Largest Reported Token Holder Share — Single Calculation

> Largest Reported Token Holder Share — Single Calculation 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).

Calculates the percentage share of the largest token holder given their token count and total circulating supply.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-bx-token-largest-holder-calculate?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-single-calculation-ced8e481
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J6OVFec7hm9WjpBwMqT73

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-single-calculation-ced8e481 -d '<json body>'
```

Example prompt: Can you calculate what percentage of the total token supply is held by the largest holder, given that they hold 250,000 tokens out of a circulating supply of 5,000,000?

## When to prefer this

Use this endpoint when you need a fast, deterministic, single-calculation result for the largest token holder's share percentage given raw token counts. Prefer it over batch endpoints when you have one specific holder/supply pair to evaluate. It is not a live blockchain scanner — use it when you already have the token counts and just need the concentration ratio computed.

## Known failure modes

- circulating_tokens of zero will fail due to exclusiveMinimum constraint — ensure supply is greater than zero
- holder_tokens or circulating_tokens exceeding the maximum value (1e16) will be rejected
- Missing required fields (holder_tokens or circulating_tokens) will result in a validation error
- Non-numeric or malformed values for token counts will cause schema validation failure

## How this service works

Largest reported token holder share — Single calculation: Single calculation 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 single calculation report.

## Output

A bounded single calculation report stating the largest token holder's percentage share of the circulating supply, derived deterministically from the supplied holder_tokens and circulating_tokens values. The result is a numeric concentration ratio, not a live scan or trade recommendation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "values": {
   "type": "object",
   "default": {
    "holder_tokens": 100000,
    "circulating_tokens": 1000000
   },
   "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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/largest-reported-token-holder-share-single-calculation-ced8e481/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)