# ONE Engine Numeric Percent Change (T4)

> ONE Engine Numeric Percent Change (T4) is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0015/call, status unknown (last checked 2026-10-02).

Computes percent change values for an array of numbers, with optional scaling, clamping, offset, and rounding controls.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/numeric/percent-change/t4?utm_source=zero.xyz
- Price: $0.0015/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-numeric-percent-change-t4-2a103df1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2xUTuBdwDL8A6LnXQtIj5

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 one-engine-numeric-percent-change-t4-2a103df1 -d '<json body>'
```

Example prompt: Calculate the percent change across these values [100, 110, 121, 133.1, 146.41], rounded to 2 decimal places.

## When to prefer this

Use this endpoint when you need a low-cost, pay-per-call computation of percent changes on a numeric array with fine-grained control over output (scaling, clamping, offset, rounding) and want to avoid standing up your own math service. Ideal for AI agents on x402/Base needing deterministic numeric transformations at $0.0015 per call.

## Known failure modes

- Array exceeds 1000 elements — request rejected
- Non-finite (NaN, Infinity) values in the input array — validation error
- Missing required 'values' field — 400 bad request
- Payment not provided or insufficient USDC — 402 payment required
- Division by zero when a value is 0 and percent change is undefined

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

A JSON object containing the computed percent change results for the input array, reflecting any applied scaling factor, offset, min/max clamping, size, and digit rounding specified in the request.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "values"
 ],
 "properties": {
  "max": {
   "type": "number"
  },
  "min": {
   "type": "number"
  },
  "size": {
   "type": "integer"
  },
  "digits": {
   "type": "integer"
  },
  "factor": {
   "type": "number"
  },
  "offset": {
   "type": "number"
  },
  "values": {
   "type": "array",
   "description": "Finite numbers, maximum 1000"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-numeric-percent-change-t4-2a103df1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)
