# Network Throughput Base-100 Index Series

> Network Throughput Base-100 Index Series 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).

Computes a base-100 indexed time series for network ingress or egress bytes across up to 200 records, grouped by network interface.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-network-throughput-index?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/network-throughput-base-100-index-series-942980b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QPO5o9rHA-VoNOWZZ7Cst

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 network-throughput-base-100-index-series-942980b4 -d '<json body>'
```

Example prompt: Can you index my network throughput data to base-100 using row-1 as the reference point? I have daily ingress_bytes readings across two interfaces — eth0 and eth1 — from 2024-01-01 to 2024-01-07, and I want to see how ingress traffic has grown relative to that starting row.

## When to prefer this

Choose this endpoint when you have raw time-series network throughput data (ingress or egress bytes) and need to express it as a relative index anchored to a specific baseline row rather than in absolute terms. It is ideal for comparing growth trends across multiple network interfaces on a common scale, producing dashboard-ready normalized metrics, or preparing data for stakeholder reports where percentage-relative values are more meaningful than raw byte counts. It does not forecast future values or enrich with external data — use it purely for local descriptive normalization.

## Known failure modes

- Fewer than 1 row submitted — minimum 1 row required
- More than 200 rows submitted — exceeds maxItems limit
- base_index references a row position that doesn't exist in the submitted data
- Date fields malformed — must match YYYY-MM-DD pattern
- ingress_bytes or egress_bytes values outside allowed range (-1T to 1T)
- Missing required fields (row_id, network_interface, date, ingress_bytes, egress_bytes) cause validation errors
- Invalid field enum value — only 'ingress_bytes' or 'egress_bytes' accepted

## How this service works

Network throughput - Base-100 series: Base-100 series for Network throughput. Up to 200 supplied typed records. Local descriptive analytics; no enrichment or forecast. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded base-100 series report.

## Output

Returns a base-100 indexed series for the selected field (ingress_bytes or egress_bytes), where the value at the specified base_index row is set to 100 and all other values are expressed relative to it. Output includes local descriptive analytics per record and grouping by network_interface, covering up to 200 input rows. No external enrichment or forecasting is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "network_interface",
     "date",
     "ingress_bytes",
     "egress_bytes"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "egress_bytes": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "ingress_bytes": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "network_interface": {
      "type": "string",
      "default": "",
      "maxLength": 80
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "egress_bytes": 1,
     "ingress_bytes": 10,
     "network_interface": "group-a"
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "egress_bytes": 2,
     "ingress_bytes": 20,
     "network_interface": "group-b"
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "egress_bytes": 3,
     "ingress_bytes": 15,
     "network_interface": "group-a"
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "egress_bytes": 4,
     "ingress_bytes": 30,
     "network_interface": "group-b"
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "ingress_bytes",
    "egress_bytes"
   ],
   "type": "string",
   "default": "ingress_bytes"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/network-throughput-base-100-index-series-942980b4/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)