# RobinX Holder Structure Diff

> RobinX Holder Structure Diff is a paid API for AI agents from api.robinx.io, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Returns a labeled diff of token holder cohorts showing who froze, added, trimmed, or exited positions, with insider/deployer/identity classification per cohort.

## Facts

- Endpoint: GET https://api.robinx.io/structure/:token
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/robinx-holder-structure-diff-8b19a7e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jmEG2P6MPclTokPXgRT8T

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 robinx-holder-structure-diff-8b19a7e5
```

Example prompt: Pull the holder structure diff for token 0x4f3a...c8d2 and tell me whether insiders or deployers are rotating out — I want to see the cohort breakdown of who froze, added, trimmed, or exited.

## When to prefer this

Use this endpoint when you need a structured, labeled breakdown of how token holder cohorts have shifted between snapshots — specifically when insider, deployer, or identity classification matters. It goes beyond raw holder counts by tagging known actors and providing a directional verdict (e.g. rotation), making it ideal for pre-trade due diligence or risk monitoring on Robinhood Chain tokens. Prefer sibling endpoints for raw on-chain stats, social sentiment, or individual wallet history.

## Known failure modes

- Invalid or non-existent token contract address returns an error or empty cohorts
- Token not tracked on Robinhood Chain (chain 4663) may return no data
- Rate limiting or payment failure (x402) if USDC payment is not processed
- Stale snapshot if no recent holder data has been indexed for the token
- Malformed 0x address format causes request rejection

## How this service works

Labeled holder-structure diff: who froze/added/trimmed/exited, with insider/deployer/identity labels

## Output

Returns a JSON object with cohort counts (how many wallets added, exited, or froze positions since last snapshot), a structure_verdict with a signal string (e.g. 'rotation'), and top-level signal label — all enriched with insider, deployer, and identity classifications per cohort.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "queryParams": {
     "type": "object",
     "required": [
      "token"
     ],
     "properties": {
      "token": {
       "type": "string",
       "description": "token contract address 0x…"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "data": {
      "cohorts": {
       "added": 5,
       "exited": 3,
       "frozen": 12
      },
      "structure_verdict": {
       "signal": "rotation"
      }
     },
     "signal": "rotation"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "data": {
  "cohorts": {
   "added": 5,
   "exited": 3,
   "frozen": 12
  },
  "structure_verdict": {
   "signal": "rotation"
  }
 },
 "signal": "rotation"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/robinx-holder-structure-diff-8b19a7e5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.robinx.io](https://www.zero.xyz/host/api.robinx.io/llms.txt)