# Ticket Escalations – Adjacent Row Changes

> Ticket Escalations – Adjacent Row Changes 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-17).

Computes adjacent row-to-row changes for ticket and escalation count data across teams and dates, returning a local descriptive analytics report.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-ticket-escalations-period-change?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ticket-escalations-adjacent-row-changes-ef294524
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_czOctyaPm1_ESeo6V4sGW

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 ticket-escalations-adjacent-row-changes-ef294524 -d '<json body>'
```

Example prompt: Can you run an adjacent row changes report on these support ticket records for teams Alpha and Beta across the past week — I want to see how escalation counts shifted from one row to the next?

## When to prefer this

Use this endpoint when you have up to 200 sequential ticket or escalation records and need to understand period-to-period (row-to-row) changes without requiring forecasting, enrichment, or external data. It is ideal for local descriptive analytics on support team data where the goal is spotting consecutive shifts or deltas in ticket or escalation volumes.

## Known failure modes

- Missing required fields (row_id, team, date, tickets, escalations) causes validation error
- Supplying more than 200 rows exceeds maxItems limit and will be rejected
- Invalid date format (not YYYY-MM-DD) triggers pattern validation failure
- Null values in the target field may produce null deltas in output
- Invalid field enum value (anything other than 'tickets' or 'escalations') causes rejection
- Empty rows array (fewer than 1 item) fails minItems constraint
- Payment of 0.01 USDC not provided or rejected causes 402 response

## How this service works

Ticket escalations - Adjacent row changes: Adjacent row changes for Ticket escalations. Up to 200 supplied typed records. Local descriptive analytics; no enrichment or forecast. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded adjacent row changes report.

## Output

Returns a bounded adjacent row changes report containing the computed delta between each consecutive pair of supplied records for the chosen field (tickets or escalations), expressed as local descriptive analytics without forecasting or external enrichment.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ticket-escalations-adjacent-row-changes-ef294524/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)