# Water Temperature Observations — Exact Row Deduplication + Numeric Row Ordering

> Water Temperature Observations — Exact Row Deduplication + 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-26).

Deduplicates and numerically orders up to 200 water temperature observation records (temperature_c, depth_m) using local analytical engines, returning two independent reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-weather-25-042?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/water-temperature-observations-exact-row-deduplication-numeric-row-b1d812ba
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tXizKUxzq4T2ju020sw2C

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 water-temperature-observations-exact-row-deduplication-numeric-row-b1d812ba -d '<json body>'
```

Example prompt: I have a batch of water temperature observation records with temperature_c and depth_m values from multiple station groups — can you deduplicate them exactly and then sort them in numeric order? I've got about 150 rows covering dates from 2026-10-01 through 2026-10-30, and I'd like the analysis run on the temperature_c field.

## When to prefer this

Choose this endpoint when you have up to 200 water temperature observation records that need exact row-level deduplication and numeric ordering of temperature_c or depth_m values, and you want two independent analytical passes on the same data for cross-validation. It operates entirely on supplied data with no external network calls, making it deterministic and privacy-safe. Prefer it over generic data-cleaning tools when your dataset specifically involves water temperature and depth measurements with station group and date fields.

## Known failure modes

- Input array exceeds 200 rows — request rejected
- Missing required fields (row_id, station_group, date, temperature_c, depth_m) cause validation errors
- Invalid date format (not YYYY-MM-DD) causes schema rejection
- Field selector not one of 'temperature_c' or 'depth_m' causes enum validation failure
- Empty rows array (minItems: 1 violated) causes rejection
- Payment of 0.01 USDC not completed via x402 protocol causes 402 response

## How this service works

Water temperature observations — Exact row deduplication + Numeric row ordering: Exact row deduplication + Numeric row ordering for supplied water temperature observations records (temperature_c, depth_m). 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 independent analytical reports per call: one showing the exact deduplicated set of water temperature rows (duplicates removed based on all field values) and one showing the rows in ascending numeric order by the selected field (temperature_c or depth_m). 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",
     "station_group",
     "date",
     "temperature_c",
     "depth_m"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "depth_m": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "station_group": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "temperature_c": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "depth_m": 1,
     "station_group": "group-a",
     "temperature_c": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "depth_m": 2,
     "station_group": "group-b",
     "temperature_c": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "depth_m": 3,
     "station_group": "group-a",
     "temperature_c": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "depth_m": 4,
     "station_group": "group-b",
     "temperature_c": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "temperature_c",
    "depth_m"
   ],
   "type": "string",
   "default": "temperature_c"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/water-temperature-observations-exact-row-deduplication-numeric-row-b1d812ba/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)