# Render Farm Usage — String Normalisation + Numeric Row Ordering

> Render Farm Usage — 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-03).

Normalises string fields and sorts rows by numeric value for up to 200 render farm usage records (node_hours, job_count), returning two analytical reports per call.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-creative-24-025?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/render-farm-usage-string-normalisation-numeric-row-ordering-086f2407
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_4etVfOmtBTrTJvo3PMWSw

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 render-farm-usage-string-normalisation-numeric-row-ordering-086f2407 -d '<json body>'
```

Example prompt: Can you normalise the string fields and rank the rows by node_hours for my render farm usage data? I have 4 records: row-1 for group-a on 2026-10-01 with 10 node_hours and 1 job, row-2 for group-b on 2026-10-02 with 20 node_hours and 2 jobs, row-3 for group-a on 2026-10-03 with 15 node_hours and 3 jobs, row-4 for group-b on 2026-10-04 with 30 node_hours and 4 jobs — give me both the string normalisation and numeric ordering reports.

## When to prefer this

Choose this endpoint when you have render farm usage records (with node_hours and job_count fields) and need both string normalisation and numeric ordering in a single low-cost call. It is ideal for pre-billing data cleanup, production reporting pipelines, or any workflow that requires standardising asset group labels and ranking compute usage rows without any live lookups or external dependencies. Best suited for batches of up to 200 rows.

## Known failure modes

- More than 200 rows submitted — request rejected with validation error
- Missing required fields (row_id, asset_group, date, node_hours, job_count) — row rejected or error returned
- Invalid date format (not YYYY-MM-DD) — validation failure
- Numeric values outside allowed range (±1,000,000,000,000) — validation error
- Invalid field enum value (not node_hours or job_count) — error returned
- Empty rows array — minimum 1 item required

## How this service works

Render farm usage — String normalisation + Numeric row ordering: String normalisation + Numeric row ordering for supplied render farm usage records (node_hours, job_count). 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: (1) a string normalisation report cleaning and standardising the asset_group and related string fields across all supplied rows, and (2) a numeric row ordering report ranking the rows by the selected numeric field (node_hours or job_count). No external data is fetched; all analysis is performed on the supplied rows only.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/render-farm-usage-string-normalisation-numeric-row-ordering-086f2407/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)