# Transport Ridership — Numeric Row Ordering + Base-100 Series

> Transport Ridership — Numeric Row Ordering + Base-100 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-26).

Assigns numeric row ordering and computes a Base-100 index series for passenger_count or service_count across up to 200 transport ridership records, returning two analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-economics-05-117?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-numeric-row-ordering-base-100-series-dec27349
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__T6fjDPsvjozIXx8EcKqc

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-numeric-row-ordering-base-100-series-dec27349 -d '<json body>'
```

Example prompt: Can you run a numeric row ordering and Base-100 index series on my transit ridership data? I have 4 rows with passenger_count values across two regions (group-a and group-b) from October 2026, and I want the indexing to start from row 0 (base_index=0), using passenger_count as the field.

## When to prefer this

Choose this endpoint when you need to both sequence transport ridership records by row order AND produce a Base-100 normalized index series in a single API call. It is ideal for transit analysts who want to compare ridership or service trends relative to a starting baseline without building their own indexing logic. Prefer it over general analytics tools when working specifically with passenger_count and service_count data up to 200 rows and needing two bundled reports at a fixed low cost.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, region, date, passenger_count, service_count) causes rejection
- Invalid date format (not YYYY-MM-DD) fails schema validation
- base_index out of range (0–199) causes error
- Null values in the selected field may affect Base-100 calculation accuracy
- Submitting zero rows fails minItems constraint

## How this service works

Transport ridership — Numeric row ordering + Base-100 series: Numeric row ordering + Base-100 series 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) a numeric row ordering of the submitted ridership records, and (2) a Base-100 index series computed on the selected field (passenger_count or service_count), where the row at base_index is set to 100 and all other rows are expressed relative to it. Results are derived entirely from 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"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transport-ridership-numeric-row-ordering-base-100-series-dec27349/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)