# Reported Locked LP-Token Fraction — Batch Calculation

> Reported Locked LP-Token Fraction — Batch Calculation 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-16).

Calculates the fraction of locked LP tokens relative to total LP tokens for multiple token observations in a single batch request.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-bx-token-lp-lock-share-batch?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reported-locked-lp-token-fraction-batch-calculation-0b909065
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_v8O36IQqVXKcFx4jJbr2p

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 reported-locked-lp-token-fraction-batch-calculation-0b909065 -d '<json body>'
```

Example prompt: Can you batch-calculate the locked LP-token fractions for these two observations: one pool with 800 locked out of 1000 total LP tokens, and another with 880 locked out of 1100 total LP tokens?

## When to prefer this

Use this endpoint when you need to compute locked LP-token fractions for multiple token observations in one call rather than making individual requests. It is ideal for bulk token screening, portfolio audits, or dashboard data pipelines where deterministic, math-based calculation from caller-supplied figures is sufficient and you do not need live on-chain scanning or trade recommendations.

## Known failure modes

- Missing required fields (locked_lp or total_lp) in any row returns a validation error
- total_lp must be greater than 0 (exclusiveMinimum); a zero value causes an error
- locked_lp exceeding total_lp may produce a fraction greater than 1, which callers should handle
- Batch exceeds 200 rows limit returns a schema validation error
- Non-numeric values in locked_lp or total_lp fields cause parsing failures

## How this service works

Reported locked LP-token fraction — Batch calculation: Batch calculation for Reported locked LP-token fraction. Supplied token observations only. Deterministic calculation or caller-threshold verdict, not a live scan, safety proof or trade recommendation. Specialised preset in a shared 50-profile, 20-operation engine. 0.01 USDC includes one bounded batch calculation report.

## Output

Returns a batch report containing the computed locked LP-token fraction (locked_lp / total_lp) for each supplied row of observations, expressed as a deterministic ratio or percentage. Results are based solely on the caller-supplied figures and represent a mathematical calculation, not a live on-chain scan or safety guarantee.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "locked_lp",
     "total_lp"
    ],
    "properties": {
     "total_lp": {
      "type": "number",
      "default": 1000,
      "maximum": 10000000000000000,
      "minimum": 0,
      "exclusiveMinimum": 0
     },
     "locked_lp": {
      "type": "number",
      "default": 800,
      "maximum": 10000000000000000,
      "minimum": 0
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "total_lp": 1000,
     "locked_lp": 800
    },
    {
     "total_lp": 1100,
     "locked_lp": 880.0000000000001
    }
   ],
   "maxItems": 200,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/reported-locked-lp-token-fraction-batch-calculation-0b909065/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)