# ONE Engine Moving Average (T2)

> ONE Engine Moving Average (T2) is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0007/call, status unknown (last checked 2026-10-02).

Computes a moving average over a sequence of up to 1000 numeric values with optional scaling, clamping, rounding, and offset controls.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/numeric/moving-average/t2?utm_source=zero.xyz
- Price: $0.0007/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-moving-average-t2-c4d51e6b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_U6LKhBJyC4xdAsRmFNEGS

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-moving-average-t2-c4d51e6b -d '<json body>'
```

Example prompt: Can you compute a 5-period moving average over these values: [10, 20, 30, 25, 40, 35, 50, 45, 60, 55], rounding results to 2 decimal places?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call moving average computation without spinning up your own math infrastructure. It is particularly useful for AI agents that need on-demand numeric smoothing of time series, sensor data, or financial series, especially when combined with clamping and rounding options in a single call. Prefer it over general-purpose compute services when cost-efficiency at micro-scale ($0.0007/call) and simplicity matter.

## Known failure modes

- Array exceeds 1000 values — request rejected
- Non-finite numbers (NaN, Infinity) in the values array cause errors
- Window size (size) larger than the input array length may produce empty or partial results
- Payment failure via x402 protocol blocks request
- Invalid types for numeric parameters cause schema validation errors

## How this service works

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

## Output

Returns a JSON object containing the computed moving average series derived from the input numeric array, reflecting the configured window size, optional min/max clamping, decimal rounding precision, multiplicative factor, and additive offset.

## 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-moving-average-t2-c4d51e6b/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)