# Largest Reported Token Holder Share — Sequential Input-Change Attribution

> Largest Reported Token Holder Share — Sequential Input-Change Attribution 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 how a change in holder_tokens or circulating_tokens sequentially shifts the largest-holder share percentage, attributing each input's contribution to the overall delta.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-bx-token-largest-holder-waterfall?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-sequential-input-change-attribution-74f62dd0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jCBHsyi1wTBoykoK0t-FW

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-sequential-input-change-attribution-74f62dd0 -d '<json body>'
```

Example prompt: Show me a sequential input-change attribution waterfall for the largest token holder share: before state was 100,000 holder tokens out of 1,000,000 circulating, and after state is 110,000 holder tokens out of 1,100,000 circulating — which input change contributed more to the shift?

## When to prefer this

Choose this endpoint when you need to understand *why* a largest-holder concentration percentage changed between two states — specifically to attribute the delta sequentially to changes in holder balance vs circulating supply. Prefer it over simple share calculators when decomposition of contributing inputs matters, or when you need a deterministic attribution waterfall rather than a point-in-time snapshot.

## Known failure modes

- circulating_tokens of zero is rejected (exclusiveMinimum:0 enforced)
- negative values for holder_tokens or circulating_tokens are invalid
- holder_tokens exceeding maximum (1e16) will be rejected
- missing required before/after sub-fields returns validation error
- payment not included or insufficient USDC results in 402 response

## How this service works

Largest reported token holder share — Sequential input-change attribution: Sequential input-change attribution 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 sequential input-change attribution report.

## Output

A bounded sequential input-change attribution report showing how changes in holder_tokens and circulating_tokens each contributed to the shift in largest-holder share percentage, with a deterministic calculation or caller-threshold verdict. Not a live scan, safety proof, or trade recommendation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "object",
   "default": {
    "holder_tokens": 110000.00000000001,
    "circulating_tokens": 1100000
   },
   "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
  },
  "before": {
   "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-sequential-input-change-attribution-74f62dd0/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)