# Business Directory Coverage — String Normalisation + Numeric Row Ordering

> Business Directory Coverage — String Normalisation + 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-11-04).

Normalises string fields and applies numeric row ordering to business directory coverage records (listed_entities, verified_entities) for up to 200 rows, returning 2 independent analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-14-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/business-directory-coverage-string-normalisation-numeric-row-ordering-942490b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u5-ykIvrQWYuFnfe4Rhcw

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 business-directory-coverage-string-normalisation-numeric-row-ordering-942490b6 -d '<json body>'
```

Example prompt: Can you normalise the company group strings and sort my business directory coverage rows numerically by listed_entities? I have 4 rows: row-1 group-a 2026-10-01 listed=10 verified=1, row-2 group-b 2026-10-02 listed=20 verified=2, row-3 group-a 2026-10-03 listed=15 verified=3, row-4 group-b 2026-10-04 listed=30 verified=4 — analyse on listed_entities.

## When to prefer this

Choose this endpoint when you need lightweight, local string normalisation and numeric ordering on business directory coverage records without requiring external data enrichment, live lookups, or ML predictions. It is best for batch preprocessing of up to 200 rows of listed/verified entity data before reporting or compliance workflows, and when a flat $0.01 USDC cost for two bundled analytical reports is acceptable.

## Known failure modes

- Missing required fields (row_id, date, company_group, listed_entities, verified_entities) returns a validation error
- More than 200 rows submitted exceeds the maxItems limit and will be rejected
- Invalid date format (not YYYY-MM-DD) causes schema validation failure
- Field selector not one of 'listed_entities' or 'verified_entities' returns an enum error
- Empty rows array (minItems: 1 not met) returns a validation error

## How this service works

Business directory coverage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied business directory coverage records (listed_entities, verified_entities). 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 independent analytical reports: one covering string normalisation of the company_group and related string fields across up to 200 supplied rows, and one providing numeric row ordering based on the selected field (listed_entities or verified_entities). No external lookups or predictions are made; all analysis uses local analytical engines on the supplied data.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/business-directory-coverage-string-normalisation-numeric-row-ordering-942490b6/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)