# On-time Dispatch Share – Adjacent Period Changes

> On-time Dispatch Share – Adjacent Period 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-14).

Computes period-over-period changes in on-time dispatch share (on-time dispatches ÷ total dispatches) for retail logistics data across up to 200 records.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-retail-dispatch-on-time-period-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/on-time-dispatch-share-adjacent-period-changes-c4264cb5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VDZhFKXM4QOpZtEEXsaBx

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 on-time-dispatch-share-adjacent-period-changes-c4264cb5 -d '<json body>'
```

Example prompt: Can you calculate the adjacent period changes in on-time dispatch share for my retail data? I have two periods: period 1 had 100 dispatches with 92 on time, and period 2 had 110 dispatches with 101 on time.

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call computation of period-over-period changes in on-time dispatch share from retail dispatch data you already have. It is ideal for batch analysis of up to 200 row-pairs without needing platform access, live order data, or custom integrations.

## Known failure modes

- Input array has fewer than 2 rows — minimum 2 rows required
- Rows exceed 200 items — request will be rejected
- dispatches value is 0 or missing — exclusiveMinimum enforces > 0
- on_time_dispatches exceeds dispatches — logically inconsistent but not schema-blocked
- Malformed JSON body — 400 error
- Payment not provided or insufficient — x402 payment required error

## How this service works

On-time dispatch share - Adjacent period changes: Adjacent period changes for On-time dispatch share. Supplied retail figures only, up to 200 records. No platform access, live rates or order execution. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded adjacent period changes report.

## Output

A bounded report showing the computed on-time dispatch share and its change between adjacent periods for each row pair in the input, based solely on supplied retail dispatch figures (no live rates or platform access).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "dispatches",
     "on_time_dispatches"
    ],
    "properties": {
     "dispatches": {
      "type": "number",
      "default": 100,
      "maximum": 1000000000000,
      "minimum": 0,
      "exclusiveMinimum": 0
     },
     "on_time_dispatches": {
      "type": "number",
      "default": 92,
      "maximum": 1000000000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "dispatches": 100,
     "on_time_dispatches": 92
    },
    {
     "dispatches": 110.00000000000001,
     "on_time_dispatches": 101.2
    },
    {
     "dispatches": 100,
     "on_time_dispatches": 92
    },
    {
     "dispatches": 110.00000000000001,
     "on_time_dispatches": 101.2
    }
   ],
   "maxItems": 200,
   "minItems": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/on-time-dispatch-share-adjacent-period-changes-c4264cb5/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)