Who runs the money, and how much is theirs
operator_checkRead-onlyIdempotent
The question that follows vault_check: who runs the money, and how much of it is their own. Free. Read ownShare with its limits, which travel inside it: the leader’s holding is readable on Hyperliquid and Drift ONLY, so elsewhere it is ABSENT and not zero, the median describes the strategies we can read rather than the manager, and a large own-share is evidence of alignment and never proof, because the address running a vault can be a treasury or a custodian holding for other people. cannotSee names whatever of that applies here. Take the slug from vault_check’s operator.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The operator’s slug, as vault_check returns it in `operator.slug`. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The operator’s name as published. Their words, not an identity we verified. | |
| says | Yes | The operator in one sentence, including what we cannot see about them — own-capital share is readable on two venues only. | |
| ownShare | No | Median share of the vault its leader holds, the count it is taken over, and what it does and does not mean. | |
| cannotSee | Yes | ||
| capitalUsd | No | Capital across every open strategy we read for this operator. Null where none of them can be priced. | |
| strategies | No | How many open and closed, and on which platforms. | |
| agentManaged | No | How many of their open strategies we have reason to call agent-managed. A COUNT of strategies, never a share of the capital. |