# Bittensor Subnet Alpha Stake Flow Analysis

> Bittensor Subnet Alpha Stake Flow Analysis is a paid API for AI agents from api.chainmarket-api.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-02).

Returns historical alpha trajectory and net stake flow (inflow/outflow) for a specific Bittensor subnet, including TAO-denominated values at current price and point-in-time pool stakes.

## Facts

- Endpoint: GET https://api.chainmarket-api.workers.dev/api/crypto/tao-subnet-stake-flows?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bittensor-subnet-alpha-stake-flow-analysis-ad098338
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5UGFNRwHFrF46c5YmKzen

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 bittensor-subnet-alpha-stake-flow-analysis-ad098338
```

Example prompt: Can you pull the stake flow data for Bittensor subnet 18 over the last 50 historical snapshots and tell me whether alpha is flowing in or out, and what the net flow is worth in TAO?

## When to prefer this

Use this endpoint when you need historical staking dynamics specifically for a Bittensor subnet, including alpha flow direction and TAO valuation — particularly for monitoring validator behavior, detecting stake migration, or researching subnet health. Prefer this over generic blockchain explorers when you need aggregated flow metrics rather than raw transaction data, and over the metagraph slice endpoint when your focus is stake economics rather than neuron-level metadata.

## Known failure modes

- Missing or invalid TAOSTATS_API_KEY returns authentication error
- Invalid or non-existent netuid returns empty or error response
- limit outside 2-100 range returns validation error
- Upstream TaoStats API unavailability causes 502 or timeout
- Requesting a subnet with insufficient snapshot history may return fewer results than requested

## How this service works

Staked alpha trajectory and net flow into a specific Bittensor subnet over historical pool snapshots: net flow in alpha (with its TAO value at the newest point's price), direction (inflow/outflow), and point-in-time pool stakes. Requires TAOSTATS_API_KEY.

## Output

Returns an array of historical pool snapshots for the specified Bittensor subnet, including the staked alpha trajectory over time, net flow direction (inflow or outflow), the net alpha amount that flowed in or out, its TAO equivalent valued at the most recent snapshot's price, and point-in-time pool stake values for each snapshot.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "limit": {
       "type": "integer",
       "default": 30,
       "maximum": 100,
       "minimum": 2,
       "description": "Number of historical snapshots"
      },
      "netuid": {
       "type": "integer",
       "minimum": 0,
       "description": "Subnet network UID (default 1)"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bittensor-subnet-alpha-stake-flow-analysis-ad098338/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.chainmarket-api.workers.dev](https://www.zero.xyz/host/api.chainmarket-api.workers.dev/llms.txt)