# Transport Ridership Data Quality Audit, String Normalisation & Numeric Interval Filter

> Transport Ridership Data Quality Audit, String Normalisation & Numeric Interval Filter 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).

Audits record quality, normalises region strings, and filters passenger_count or service_count by numeric interval for up to 200 transport ridership rows, returning three independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-economics-05-197?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-data-quality-audit-string-normalisation-numeric-2c4b64b1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hBvQqodsWwqSKBw9k9d1N

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-data-quality-audit-string-normalisation-numeric-2c4b64b1 -d '<json body>'
```

Example prompt: Can you run a record quality audit, string normalisation, and numeric interval filter on my transport ridership data — here are 50 rows with row_id, region, date, passenger_count, and service_count — I want to filter on passenger_count between 0 and 500?

## When to prefer this

Choose this endpoint when you need three simultaneous local analytical operations — quality audit, string normalisation, and numeric interval filtering — on transport ridership data in a single $0.01 call. It is ideal for pre-processing transit datasets before ingestion into dashboards or pipelines, particularly when you want to catch bad records, standardise region labels, and range-filter numeric fields in one pass without making external API calls or incurring per-operation costs.

## Known failure modes

- Submitting more than 200 rows returns an error — batch must be split
- Missing required fields (row_id, region, date, passenger_count, service_count) causes row-level validation failure
- Invalid date format (not YYYY-MM-DD) triggers schema rejection
- minimum greater than maximum causes the interval filter to return no matching rows
- Null numeric values for both passenger_count and service_count may degrade numeric filter results
- Payment failure or insufficient USDC balance prevents processing

## How this service works

Transport ridership — Record quality audit + String normalisation + Numeric interval filter: Record quality audit + String normalisation + Numeric interval filter for supplied transport ridership records (passenger_count, service_count). Up to 200 rows; 3 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 3 supplied-data reports for up to 200 rows.

## Output

Three independent analytical reports: (1) a record quality audit flagging missing values, malformed dates, or schema violations across the submitted rows; (2) a string normalisation report showing standardised region name variants; (3) a numeric interval filter report listing which rows fall within the specified minimum–maximum range for the chosen field (passenger_count or service_count). All results are derived locally from the submitted 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"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/transport-ridership-data-quality-audit-string-normalisation-numeric-2c4b64b1/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)