# Road Segment Observations — Numeric Interval Filter + Secondary-Measure Weighted Mean

> Road Segment Observations — Numeric Interval Filter + Secondary-Measure Weighted Mean 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).

Filters road segment observation rows by a numeric interval on a chosen field and computes a secondary-measure weighted mean, returning two analytical reports for up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-15-132?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-numeric-interval-filter-secondary-measure-4b692017
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dhSiT8Id-sijzUYnPrPey

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-numeric-interval-filter-secondary-measure-4b692017 -d '<json body>'
```

Example prompt: I have road segment observations with length_m and travel_seconds — can you filter the records where length_m is between 10 and 500, then compute the secondary-measure weighted mean using travel_seconds as the field, for these up to 200 rows I'll supply?

## When to prefer this

Choose this endpoint when you have pre-collected road segment observation data (length and travel time) and need both a numeric interval filter and a secondary-measure weighted mean in a single call, without any external data lookup or prediction. Ideal for batch offline analysis of up to 200 rows at low cost ($0.01 USDC for two reports). Not suitable for real-time traffic data retrieval, route planning, or live sensor feeds.

## Known failure modes

- More than 200 rows supplied — request rejected or truncated
- Invalid date format (must be YYYY-MM-DD) — schema validation error
- Minimum bound greater than maximum bound — empty filtered result set
- Missing required fields (row_id, date, length_m, travel_seconds) — validation error
- All rows filtered out by interval — weighted mean undefined or empty report
- Null values in length_m or travel_seconds may affect weighted mean computation

## How this service works

Road segment observations — Numeric interval filter + Secondary-measure weighted mean: Numeric interval filter + Secondary-measure weighted mean for supplied road segment observations records (length_m, travel_seconds). 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: one covering a numeric interval filter applied to the chosen field (length_m or travel_seconds) within the specified minimum/maximum bounds, and one covering the secondary-measure weighted mean computed across the filtered road segment observation rows. Results are derived entirely from the supplied data (up to 200 rows) 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"
  },
  "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/road-segment-observations-numeric-interval-filter-secondary-measure-4b692017/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)
