# Revenue per Visitor – Adjacent Period Changes

> Revenue per Visitor – 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-15).

Calculates adjacent period-over-period changes in revenue per visitor from supplied retail row data.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-sector-retail-revenue-visitor-period-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/revenue-per-visitor-adjacent-period-changes-956a7a7d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-XwhBIIoaMUOKsz4JhkBo

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 revenue-per-visitor-adjacent-period-changes-956a7a7d -d '<json body>'
```

Example prompt: I have four periods of retail data — period 1: revenue $3000, visitors 1000; period 2: revenue $3300, visitors 1100; period 3: revenue $3000, visitors 1000; period 4: revenue $3300, visitors 1100 — can you calculate the adjacent period changes in revenue per visitor across these?

## When to prefer this

Choose this endpoint when you need a local, offline calculation of adjacent period revenue-per-visitor changes from supplied retail figures — no live platform access, account credentials, or inventory lookups required. Ideal for scenario modeling, historical analysis, or quick period-over-period comparisons where you already have the raw revenue and visitor data.

## Known failure modes

- Fewer than 2 rows supplied — minimum 2 rows required
- Visitors value of 0 or negative — visitors must be strictly positive (exclusiveMinimum: 0)
- More than 200 rows supplied — exceeds maxItems limit
- Revenue or visitors values outside allowed range (±1 trillion)
- Malformed or missing required fields (revenue or visitors) in any row

## How this service works

Revenue per visitor - Adjacent period changes: Adjacent period changes for Revenue per visitor. Supplied retail figures only. Local calculation and scenario analysis; no live inventory, account access, platform fee lookup or order execution. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded adjacent period changes deliverable.

## Output

Returns computed adjacent period-over-period changes in the revenue per visitor metric for each consecutive pair of supplied retail period rows, enabling trend and scenario analysis without live platform or inventory data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "revenue",
     "visitors"
    ],
    "properties": {
     "revenue": {
      "type": "number",
      "default": 3000,
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "visitors": {
      "type": "number",
      "default": 1000,
      "maximum": 1000000000000,
      "minimum": 0,
      "exclusiveMinimum": 0
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "revenue": 3000,
     "visitors": 1000
    },
    {
     "revenue": 3300.0000000000005,
     "visitors": 1100
    },
    {
     "revenue": 3000,
     "visitors": 1000
    },
    {
     "revenue": 3300.0000000000005,
     "visitors": 1100
    }
   ],
   "maxItems": 200,
   "minItems": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/revenue-per-visitor-adjacent-period-changes-956a7a7d/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)