# Held-Order Release Share Batch Calculator

> Held-Order Release Share Batch Calculator 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-12).

Calculates held-order release share ratios for up to 200 retail order records in a single batch operation

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ar-retail-held-order-release-batch?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/held-order-release-share-batch-calculator-277a16d5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Da1QNPWBkz-76bh-BoAKl

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 held-order-release-share-batch-calculator-277a16d5 -d '<json body>'
```

Example prompt: Can you calculate the held-order release share for these retail figures — I have two batches: 100 held with 75 released, and 110 held with 82.5 released?

## When to prefer this

Choose this endpoint when you need to compute release share ratios for held retail orders across multiple records in one call (up to 200 rows), and you only have raw held/released order count figures available — no live platform access, live rates, or order execution is needed. Ideal for offline analytics, periodic reporting, or benchmarking scenarios where batch efficiency matters over real-time data.

## Known failure modes

- More than 200 rows submitted — maxItems limit exceeded, request rejected
- held_orders value of 0 or below — exclusiveMinimum constraint violation
- Missing required fields held_orders or released_orders in any row — validation error
- Non-numeric values passed for order counts — schema type error
- Payment not completed or insufficient USDC balance — x402 payment required error

## How this service works

Held-order release share - Batch calculation: Batch calculation for Held-order release share. Supplied retail figures only, up to 200 records. No platform access, live rates or order execution. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded batch calculation report.

## Output

A bounded batch calculation report containing held-order release share metrics (ratios/percentages) for each submitted row, covering up to 200 input records of held and released order counts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "held_orders",
     "released_orders"
    ],
    "properties": {
     "held_orders": {
      "type": "number",
      "default": 100,
      "maximum": 1000000000000,
      "minimum": 0,
      "exclusiveMinimum": 0
     },
     "released_orders": {
      "type": "number",
      "default": 75,
      "maximum": 1000000000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "held_orders": 100,
     "released_orders": 75
    },
    {
     "held_orders": 110.00000000000001,
     "released_orders": 82.5
    }
   ],
   "maxItems": 200,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/held-order-release-share-batch-calculator-277a16d5/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)