# Account Research Coverage — String Normalisation + Numeric Row Ordering

> Account Research 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-10-19).

Normalises company group strings and orders rows numerically for account research coverage data (researched_accounts, target_accounts) across up to 200 rows, producing 2 analytical reports per call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-company-08-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/account-research-coverage-string-normalisation-numeric-row-ordering-4819085a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q3vBX9Uu_VFFLo2EDj37y

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 account-research-coverage-string-normalisation-numeric-row-ordering-4819085a -d '<json body>'
```

Example prompt: Can you clean up the company group names and sort these account research records numerically by researched_accounts? I have 4 rows: row-1 group-a 2026-10-01 with 10 researched and 1 target, row-2 group-b 2026-10-02 with 20 researched and 2 target, row-3 group-a 2026-10-03 with 15 researched and 3 target, row-4 group-b 2026-10-04 with 30 researched and 4 target — give me two reports covering both fields.

## When to prefer this

Choose this endpoint when you have raw account research coverage records with inconsistent company group string formatting and need both string normalisation and numeric ordering applied in a single low-cost call. It is ideal for sales ops or B2B data quality workflows where you want structured reports on researched_accounts and target_accounts without requiring live data lookups, external enrichment, or predictive modelling. At $0.01 USDC for up to 200 rows and two reports, it is cost-effective for batch cleaning of coverage datasets.

## Known failure modes

- Missing required fields (row_id, company_group, date, researched_accounts, target_accounts) causes validation error
- More than 200 rows submitted exceeds the maxItems limit and will be rejected
- Invalid date format (not YYYY-MM-DD) triggers pattern validation failure
- Numeric values outside ±1,000,000,000,000 are rejected by schema bounds
- Empty rows array (minItems: 1 not met) returns error
- Payment of 0.01 USDC not included or rejected blocks the request

## How this service works

Account research coverage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied account research coverage records (researched_accounts, target_accounts). 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 per call: one for researched_accounts and one for target_accounts. Each report contains string-normalised company_group labels and rows ordered numerically by the selected metric. No live lookups, predictions, or external actions are performed — 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",
     "researched_accounts",
     "target_accounts"
    ],
    "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
     },
     "target_accounts": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "researched_accounts": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "company_group": "group-a",
     "target_accounts": 1,
     "researched_accounts": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "company_group": "group-b",
     "target_accounts": 2,
     "researched_accounts": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "company_group": "group-a",
     "target_accounts": 3,
     "researched_accounts": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "company_group": "group-b",
     "target_accounts": 4,
     "researched_accounts": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "researched_accounts",
    "target_accounts"
   ],
   "type": "string",
   "default": "researched_accounts"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/account-research-coverage-string-normalisation-numeric-row-ordering-4819085a/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)