# Customer Segment Observations — Category Frequencies + Numeric Row Ordering

> Customer Segment Observations — Category Frequencies + 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-20).

Analyzes up to 200 customer segment observation records to produce two reports: category frequency counts for company_group and numeric row ordering for account_count or revenue_amount.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-16-100?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/customer-segment-observations-category-frequencies-numeric-row-ordering-40c75f68
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ijq680D1rznQjqo5o9c3u

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 customer-segment-observations-category-frequencies-numeric-row-ordering-40c75f68 -d '<json body>'
```

Example prompt: I have 4 rows of customer segment data — row-1 group-a 2026-10-01 with 10 accounts and $1 revenue, row-2 group-b 2026-10-02 with 20 accounts and $2 revenue, row-3 group-a 2026-10-03 with 15 accounts and $3 revenue, row-4 group-b 2026-10-04 with 30 accounts and $4 revenue — can you give me both a category frequency breakdown by company_group and a numeric row ordering by account_count?

## When to prefer this

Choose this endpoint when you have up to 200 customer segment observation records and need both a category frequency distribution of company groups and a numeric row ranking by account_count or revenue_amount in a single low-cost call ($0.01 USDC). Ideal for local, self-contained analytics with no need for external data lookups or predictions.

## Known failure modes

- More than 200 rows submitted — request exceeds row limit
- Missing required fields (row_id, company_group, date, account_count, or revenue_amount) — validation error
- Invalid date format (must be YYYY-MM-DD) — schema validation failure
- Numeric field values outside allowed range (-1,000,000,000,000 to 1,000,000,000,000) — range error
- Invalid field enum value — must be account_count or revenue_amount

## How this service works

Customer segment observations — Category frequencies + Numeric row ordering: Category frequencies + Numeric row ordering for supplied customer segment observations records (account_count, revenue_amount). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.

## Output

Two analytical reports: (1) a category frequency table showing how often each company_group value appears across the supplied rows, and (2) a numeric row ordering ranking all rows by the selected numeric field (account_count or revenue_amount), all computed locally with no external lookups.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/customer-segment-observations-category-frequencies-numeric-row-ordering-40c75f68/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)