# Road Segment Observations — Record Quality Audit + String Normalisation + Base-100 Series

> Road Segment Observations — Record Quality Audit + String Normalisation + 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-11-02).

Runs three local analytical reports on road segment observation data: a record quality audit, string normalisation, and a base-100 index series for up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-15-201?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/road-segment-observations-record-quality-audit-string-normalisation-a74544db
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_A2StseHyTt6As4sw7yAUR

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 road-segment-observations-record-quality-audit-string-normalisation-a74544db -d '<json body>'
```

Example prompt: Can you run a record quality audit, string normalisation, and base-100 index series on my road segment observations? I have rows with row_id, station_group, date, length_m, and travel_seconds — I want to index on the length_m field starting from row index 0.

## When to prefer this

Choose this endpoint when you need to simultaneously audit data quality, normalise strings, and produce a base-100 index series on road segment observation records in a single paid call. It is particularly suited for transportation data pipelines where you want three diagnostic reports at once without external data lookups or predictions. Prefer it over single-purpose analytics endpoints when your dataset is under 200 rows and covers length_m or travel_seconds measurements by station group and date.

## Known failure modes

- Submitting more than 200 rows returns a validation error
- Missing required row fields (row_id, date, length_m, travel_seconds) causes schema rejection
- Invalid date format (not YYYY-MM-DD) triggers pattern validation failure
- base_index out of range (>199 or negative) causes an error
- Empty rows array is rejected by minItems constraint
- Extremely large or small numeric values near limits may cause edge-case results

## How this service works

Road segment observations — Record quality audit + String normalisation + Base-100 series: Record quality audit + String normalisation + Base-100 series for supplied road segment observations records (length_m, travel_seconds). 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

Returns three independent analytical reports for the submitted road segment rows: (1) a record quality audit flagging missing, out-of-range, or malformed values; (2) a string normalisation report standardising text fields like station_group; and (3) a base-100 index series for the chosen numeric field (length_m or travel_seconds) anchored at the specified base_index row. All processing is local with no external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "station_group",
     "date",
     "length_m",
     "travel_seconds"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "length_m": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "station_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "travel_seconds": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "length_m": 10,
     "station_group": "group-a",
     "travel_seconds": 1
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "length_m": 20,
     "station_group": "group-b",
     "travel_seconds": 2
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "length_m": 15,
     "station_group": "group-a",
     "travel_seconds": 3
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "length_m": 30,
     "station_group": "group-b",
     "travel_seconds": 4
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "length_m",
    "travel_seconds"
   ],
   "type": "string",
   "default": "length_m"
  },
  "base_index": {
   "type": "integer",
   "default": 0,
   "maximum": 199,
   "minimum": 0
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/road-segment-observations-record-quality-audit-string-normalisation-a74544db/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)