# Service Availability Observations – Numeric Row Ordering

> Service Availability Observations – Numeric Row Ordering 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-13).

Sorts up to 200 service availability observation records by a chosen numeric field (observed_minutes or outage_minutes) and returns them in ranked order.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-analytics-service-availability-sort?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/service-availability-observations-numeric-row-ordering-7f003d49
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fa68ZhcdUPwFwsy0ZkMtm

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 service-availability-observations-numeric-row-ordering-7f003d49 -d '<json body>'
```

Example prompt: Sort these service availability records by outage_minutes — I have about 10 rows covering services group-a and group-b from Oct 1–10, and I want to see which days had the worst outages ranked from highest to lowest.

## When to prefer this

Choose this endpoint when you have up to 200 service availability records and need a simple numeric sort by either observed or outage minutes — it is fast, cheap ($0.01 USDC), and requires no external data. Prefer it over general-purpose analytics tools when you want a bounded, reproducible row-ordering result with no side effects and no enrichment overhead.

## Known failure modes

- Missing required fields (row_id, service, date, observed_minutes, outage_minutes) returns a validation error
- More than 200 rows submitted exceeds the maxItems limit and will be rejected
- Invalid date format (not YYYY-MM-DD) triggers a pattern validation failure
- Invalid field enum value (anything other than observed_minutes or outage_minutes) causes a schema error
- Empty rows array (minItems:1 not met) returns an error
- Payment failure via x402 protocol results in no response

## How this service works

Service availability observations - Numeric row ordering: Numeric row ordering for Service availability observations. 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 numeric row ordering report.

## Output

Returns the submitted service availability observation rows reordered numerically by the specified field (observed_minutes or outage_minutes), enabling quick identification of best and worst performing periods without any external enrichment or forecasting.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/service-availability-observations-numeric-row-ordering-7f003d49/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)