# Endpoint Telemetry — Adjacent Row Changes + Secondary-Measure Weighted Mean

> Endpoint Telemetry — Adjacent Row Changes + 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-10-31).

Computes adjacent row changes and reporting_agents-weighted mean for endpoint telemetry records (agent_count, reporting_agents) across up to 200 rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-security-15-159?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/endpoint-telemetry-adjacent-row-changes-secondary-measure-weighted-mean-2982644e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__W-xP0FHAHllhH6X8qE5j

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 endpoint-telemetry-adjacent-row-changes-secondary-measure-weighted-mean-2982644e -d '<json body>'
```

Example prompt: I have endpoint telemetry rows with agent_count and reporting_agents values — can you run adjacent row changes and a reporting_agents-weighted mean on this dataset? Here are my rows: row-1 on 2026-10-01 with agent_count 10 and reporting_agents 1, row-2 on 2026-10-02 with agent_count 20 and reporting_agents 2, row-3 on 2026-10-03 with agent_count 15 and reporting_agents 3. Analyze the agent_count field.

## When to prefer this

Choose this endpoint when you have endpoint telemetry records with agent_count and reporting_agents numeric fields and need both adjacent row-change analysis and a weighted mean in a single low-cost call. It is ideal for operational monitoring workflows where you want to detect day-over-day shifts and compute an importance-weighted average without setting up your own analytics pipeline. Prefer this over general-purpose analytics tools when working within an x402 micropayment agent workflow at $0.01 per call for up to 200 rows.

## Known failure modes

- More than 200 rows submitted — request rejected with validation error
- Missing required row fields (row_id, date, agent_count, reporting_agents, control_group) — schema validation failure
- Invalid date format (must match YYYY-MM-DD pattern) — pattern validation error
- Field selector not in allowed enum (agent_count or reporting_agents) — enum validation error
- Numeric values outside allowed range (-1e12 to 1e12) — range validation error
- Empty rows array (minItems: 1 not met) — validation error

## How this service works

Endpoint telemetry — Adjacent row changes + Secondary-measure weighted mean: Adjacent row changes + Secondary-measure weighted mean for supplied endpoint telemetry records (agent_count, reporting_agents). 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

Returns two analytical reports for the supplied telemetry rows: (1) adjacent row changes showing the delta between consecutive rows for the selected field, and (2) a secondary-measure weighted mean of the selected field weighted by the companion measure. Results are computed locally with no external data or predictions, covering up to 200 input rows per call.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/endpoint-telemetry-adjacent-row-changes-secondary-measure-weighted-mean-2982644e/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)