# Transport Ridership — Duplicate Key Report + Numeric Row Ordering

> Transport Ridership — Duplicate Key Report + Numeric Row Ordering 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-30).

Analyzes up to 200 transport ridership records to produce a duplicate key report and a numeric row ordering report for passenger_count or service_count fields.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-economics-05-058?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/transport-ridership-duplicate-key-report-numeric-row-ordering-7dbfabd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kQ_uHSq8Lr3YAAg5C5YBU

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-duplicate-key-report-numeric-row-ordering-7dbfabd7 -d '<json body>'
```

Example prompt: Can you run a duplicate key check and numeric row ordering on my transit ridership data — here are 50 rows with row_id, region, date, passenger_count, and service_count — and sort by passenger_count?

## When to prefer this

Choose this endpoint when you need both duplicate key detection and numeric ordering of transport ridership data in a single call for up to 200 rows. It is ideal for pre-processing or auditing transit datasets before ingestion, without requiring any external data sources or live lookups. Prefer it over general-purpose data tools when you want a cost-effective, deterministic, offline analysis of ridership records.

## Known failure modes

- Exceeding 200 rows returns a validation error
- Missing required fields (row_id, region, date, passenger_count, service_count) causes schema rejection
- Invalid date format (not YYYY-MM-DD) triggers a pattern validation error
- Numeric values outside the allowed range (-1e12 to 1e12) are rejected
- Empty rows array (minItems:1 not met) returns an error

## How this service works

Transport ridership — Duplicate key report + Numeric row ordering: Duplicate key report + Numeric row ordering 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

Two analytical reports: (1) a duplicate key report identifying row_ids that appear more than once in the submitted dataset, and (2) a numeric row ordering report that ranks all submitted rows by the chosen field (passenger_count or service_count), all computed locally without 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-duplicate-key-report-numeric-row-ordering-7dbfabd7/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)