# Network Throughput Keyed Dataset Comparison

> Network Throughput Keyed Dataset Comparison 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-17).

Compares two keyed datasets of network throughput records (ingress/egress bytes by interface and date), returning local descriptive analytics highlighting differences between them.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-network-throughput-compare?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/network-throughput-keyed-dataset-comparison-c5ee8abe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6qduAPhHV71f8XBFkTWGe

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-keyed-dataset-comparison-c5ee8abe -d '<json body>'
```

Example prompt: Compare these two batches of network throughput records — the first has daily ingress and egress bytes for eth0 and eth1 from last week, and the second has the same interfaces from this week — and tell me what changed between them.

## When to prefer this

Choose this endpoint when you have two structured sets of network throughput records keyed by row_id and need a local, self-contained statistical comparison — no external data sources, no forecasting. It is ideal for before/after change analysis, A/B interface comparisons, or period-over-period regression checks on up to 200 records per dataset at minimal cost ($0.01 USDC).

## Known failure modes

- Missing required fields (row_id, network_interface, date, ingress_bytes, egress_bytes) cause validation errors
- Submitting more than 200 rows in either dataset exceeds the maxItems limit
- Date strings not matching YYYY-MM-DD pattern are rejected
- Numeric byte values outside ±1,000,000,000,000 are rejected
- Empty rows array (minItems:1 not met) returns an error
- Mismatched row_id keys between datasets may result in unmatched rows with no comparison output

## How this service works

Network throughput - Keyed dataset comparison: Keyed dataset comparison 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 keyed dataset comparison report.

## Output

A bounded keyed dataset comparison report containing descriptive analytics for each matched row/key, including per-record differences in ingress_bytes and egress_bytes, summary statistics per network_interface group, and aggregate deltas between the two supplied datasets. No forecasting or external enrichment 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
  },
  "other": {
   "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
     }
    },
    "additionalPropert
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/network-throughput-keyed-dataset-comparison-c5ee8abe/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)