# Transport Ridership — Category Frequencies + Keyed Dataset Comparison

> Transport Ridership — Category Frequencies + 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-25).

Computes category frequency distributions and performs a keyed row-by-row comparison between two transport ridership datasets (passenger_count, service_count) for up to 200 rows each.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-economics-05-111?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transport-ridership-category-frequencies-keyed-dataset-comparison-85b3c24d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DJOECVMPhWrPy0Gw-EoiT

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 transport-ridership-category-frequencies-keyed-dataset-comparison-85b3c24d -d '<json body>'
```

Example prompt: I have two sets of transport ridership records — each up to 200 rows with region, date, passenger_count, and service_count — can you run category frequency analysis and compare the two datasets row-by-row by key to spot differences?

## When to prefer this

Choose this endpoint when you need both a categorical frequency profile and a direct keyed comparison between two transport ridership snapshots in a single call, without requiring any external data sources, live lookups, or predictions. It is ideal for detecting changes between dataset versions and understanding regional distribution of ridership records when you already have structured data with passenger_count and service_count fields.

## Known failure modes

- Exceeding 200 rows per dataset returns a validation error
- Missing required fields (row_id, region, date, passenger_count, service_count) causes rejection
- Invalid date format (non-YYYY-MM-DD) fails schema validation
- Mismatched row_ids between datasets may result in unmatched rows in the comparison report
- Payment of 0.01 USDC not provided returns 402 Payment Required

## How this service works

Transport ridership — Category frequencies + Keyed dataset comparison: Category frequencies + Keyed dataset comparison for supplied transport ridership records (passenger_count, service_count). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.

## Output

Returns two independent analytical reports: (1) a category frequency report showing how often each region or categorical value appears in the submitted ridership records, and (2) a keyed dataset comparison report highlighting row-by-row differences in passenger_count and service_count between the two supplied datasets, matched by row_id.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "region",
     "date",
     "passenger_count",
     "service_count"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "region": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "service_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "passenger_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "region": "group-a",
     "row_id": "row-1",
     "service_count": 1,
     "passenger_count": 10
    },
    {
     "date": "2026-10-02",
     "region": "group-b",
     "row_id": "row-2",
     "service_count": 2,
     "passenger_count": 20
    },
    {
     "date": "2026-10-03",
     "region": "group-a",
     "row_id": "row-3",
     "service_count": 3,
     "passenger_count": 15
    },
    {
     "date": "2026-10-04",
     "region": "group-b",
     "row_id": "row-4",
     "service_count": 4,
     "passenger_count": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "other": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "region",
     "date",
     "passenger_count",
     "service_count"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "region": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "service_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "passenger_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01
… (truncated)
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transport-ridership-category-frequencies-keyed-dataset-comparison-85b3c24d/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)