# Network Throughput Date-by-Category Pivot

> Network Throughput Date-by-Category Pivot 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).

Generates a date-by-category pivot table for network throughput data (ingress/egress bytes) across network interfaces, using up to 200 supplied records.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-network-throughput-pivot?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-date-by-category-pivot-7749ea24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_01305Qj5OYIACbUB4gOI3

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-date-by-category-pivot-7749ea24 -d '<json body>'
```

Example prompt: I have daily network throughput records for two interfaces—take these rows with date, ingress_bytes, and egress_bytes fields and give me a date-by-interface pivot table for ingress_bytes so I can see how each network interface compares day by day.

## When to prefer this

Choose this endpoint when you have raw network throughput records with per-row date and network interface fields and need a quick local pivot table—no ML, no forecasting, no external data enrichment. Ideal for IT teams or analytics agents doing descriptive summarization of interface-level bandwidth data across dates without needing a full BI tool.

## Known failure modes

- Empty or missing rows array returns an error
- More than 200 rows submitted exceeds the maxItems limit
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- row_id missing or empty string triggers required field error
- ingress_bytes or egress_bytes values outside ±1,000,000,000,000 are rejected
- Invalid field enum value (anything other than ingress_bytes or egress_bytes) causes error
- Payment of 0.01 USDC not completed results in 402 Payment Required response

## How this service works

Network throughput - Date by category pivot: Date by category pivot 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 date by category pivot report.

## Output

A date-by-category pivot table where rows represent dates and columns represent distinct network_interface values, with each cell containing the aggregated ingress_bytes or egress_bytes value for that date-interface combination. Up to 200 input records are processed locally with no external enrichment or forecasting.

## 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"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/network-throughput-date-by-category-pivot-7749ea24/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)