# Transport Ridership — Adjacent Row Changes + Date by Category Pivot

> Transport Ridership — Adjacent Row Changes + 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-26).

Runs two local analytical reports on transport ridership data: adjacent row-to-row change detection and a date-by-category pivot table, for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-economics-05-160?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transport-ridership-adjacent-row-changes-date-by-category-pivot-f1b32272
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ckt1iRbnLdycgKoy-hr-H

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-adjacent-row-changes-date-by-category-pivot-f1b32272 -d '<json body>'
```

Example prompt: I have a list of up to 50 transport ridership records with region, date, passenger_count, and service_count — can you run both an adjacent row changes report and a date-by-category pivot on passenger_count for me?

## When to prefer this

Choose this endpoint when you have transport ridership data (up to 200 rows) and need both sequential row-change analysis and a date-by-region pivot in a single low-cost call. It is ideal for transit analysts who want quick local computation without live data lookups or external integrations. Prefer it over generic analytics tools when your data already contains passenger_count and service_count fields keyed by region and date.

## Known failure modes

- More than 200 rows submitted — exceeds maxItems limit
- Missing required fields (row_id, region, date, passenger_count, or service_count) on any row
- Invalid date format (must match YYYY-MM-DD pattern)
- Invalid field selector — must be 'passenger_count' or 'service_count'
- Empty rows array — minItems is 1
- Numeric values outside allowed range (±1,000,000,000,000)

## How this service works

Transport ridership — Adjacent row changes + Date by category pivot: Adjacent row changes + Date by category pivot 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 analytical reports: (1) an adjacent row changes report showing the difference in the selected metric (passenger_count or service_count) between consecutive rows, and (2) a date-by-category pivot table cross-tabulating dates against region categories with the selected metric values. Both reports are computed locally on the supplied data with no external lookups.

## 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
  },
  "field": {
   "enum": [
    "passenger_count",
    "service_count"
   ],
   "type": "string",
   "default": "passenger_count"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transport-ridership-adjacent-row-changes-date-by-category-pivot-f1b32272/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)