# Observed Unit Sales Velocity – Record Ranking

> Observed Unit Sales Velocity – Record Ranking 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-16).

Ranks up to 200 retail records by their observed unit sales velocity (units sold per day), returning a bounded ranking report.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-retail-unit-sales-velocity-rank?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/observed-unit-sales-velocity-record-ranking-085d49bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_3ghymb-3HkQI9QadVH7Xe

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 observed-unit-sales-velocity-record-ranking-085d49bc -d '<json body>'
```

Example prompt: Can you rank these 4 sales records by their unit sales velocity? Record 1: 84 units sold over 7 days; Record 2: 92 units sold over 7.7 days; Record 3: 150 units sold over 10 days; Record 4: 60 units sold over 5 days.

## When to prefer this

Choose this endpoint when you need a ranked comparison of retail sales velocity across multiple records using only observed unit counts and observation windows, without requiring live platform data, pricing feeds, or order execution. Ideal for offline or batch-style retail analytics where you have up to 200 discrete sales observations to compare.

## Known failure modes

- Fewer than 2 rows supplied — minimum array size is 2 records
- More than 200 rows supplied — maximum is 200 records per call
- observed_days set to 0 or negative — exclusiveMinimum enforced, must be greater than 0
- Non-numeric values in sold_units or observed_days fields cause schema validation failure
- sold_units or observed_days exceed 1,000,000,000,000 — maximum boundary violation

## How this service works

Observed unit sales velocity - Record ranking: Record ranking for Observed unit sales velocity. 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 record ranking report.

## Output

A bounded ranking report listing the input retail records ordered by their computed unit sales velocity (units sold per day), with relative rank positions assigned to each record. Up to 200 records supported per call. No live pricing, platform access, or order execution data is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "sold_units",
     "observed_days"
    ],
    "properties": {
     "sold_units": {
      "type": "number",
      "default": 84,
      "maximum": 1000000000000,
      "minimum": 0
     },
     "observed_days": {
      "type": "number",
      "default": 7,
      "maximum": 1000000000000,
      "minimum": 0,
      "exclusiveMinimum": 0
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "sold_units": 84,
     "observed_days": 7
    },
    {
     "sold_units": 92.4,
     "observed_days": 7.700000000000001
    },
    {
     "sold_units": 84,
     "observed_days": 7
    },
    {
     "sold_units": 92.4,
     "observed_days": 7.700000000000001
    }
   ],
   "maxItems": 200,
   "minItems": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/observed-unit-sales-velocity-record-ranking-085d49bc/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)