# Project Effort String Normalisation + Numeric Row Ordering

> Project Effort 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-25).

Normalises team group strings and orders rows numerically by estimated_hours or actual_hours for up to 200 project effort records, producing two local analytical reports.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-operations-01-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/project-effort-string-normalisation-numeric-row-ordering-63cbced4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_amounfiYWB0977PUt7Itz

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 project-effort-string-normalisation-numeric-row-ordering-63cbced4 -d '<json body>'
```

Example prompt: Can you normalise the team group strings and sort these project effort rows by estimated_hours? I have 4 rows: row-1 for group-a on 2026-10-01 with 10 estimated and 1 actual hours, row-2 for group-b on 2026-10-02 with 20 estimated and 2 actual, row-3 for group-a on 2026-10-03 with 15 estimated and 3 actual, and row-4 for group-b on 2026-10-04 with 30 estimated and 4 actual hours.

## When to prefer this

Choose this endpoint when you need lightweight, offline string normalisation of team group labels combined with numeric ordering of project effort rows (estimated or actual hours) and want both operations in a single cheap call ($0.01 USDC for two reports). Ideal for pre-processing effort data before reporting or visualisation, without requiring any live data lookups, predictions, or external integrations.

## Known failure modes

- More than 200 rows submitted — request rejected with validation error
- Missing required fields (row_id, date, estimated_hours, actual_hours) — row rejected or error returned
- Invalid date format not matching YYYY-MM-DD — schema validation failure
- Numeric values outside allowed range — validation error
- Invalid field enum value — schema rejection

## How this service works

Project effort — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied project effort records (estimated_hours, actual_hours). 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: one with team_group strings normalised (e.g. consistent casing and whitespace), and one with the input rows reordered numerically by the selected field (estimated_hours or actual_hours). No external lookups or predictions are made; all computation is local.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/project-effort-string-normalisation-numeric-row-ordering-63cbced4/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)