# ONE Engine Numeric Clamp Top-10

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

Clamps an array of up to 1000 numbers to a specified range and returns the top 10 results, with optional scaling, rounding, and offset transformations.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/numeric/clamp/t10?utm_source=zero.xyz
- Price: $0.03/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-clamp-top-10-cac1571e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iyRRsDeqxTPvC_6dEYBqV

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-clamp-top-10-cac1571e -d '<json body>'
```

Example prompt: Clamp these numbers between 0 and 100, scale by 1.5, round to 2 decimal places, and give me the top 10: [45.3, 120, -5, 78.9, 200, 33.1, 99, 0.5, 150, 88.2, 42, 67, 11, 95, 130]

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call numeric clamping and ranking operation without spinning up your own compute. Ideal for AI agents that occasionally need to bound, scale, and rank numeric arrays in real-time pipelines, especially when integrated with x402 micropayment flows on Base. Best for arrays up to 1000 numbers where you want the top 10 results after transformation.

## Known failure modes

- Array exceeds 1000 elements — request rejected
- Non-finite numbers (Infinity, NaN) in the values array cause validation errors
- Missing required 'values' field returns a 400 error
- Payment not included or insufficient USDC triggers a 402 Payment Required response
- Invalid types for min/max/factor/offset parameters cause schema 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 top 10 numeric values from the input array after applying clamping (min/max bounds), optional scaling (factor), optional offset, and optional decimal rounding — sorted in descending order.

## 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-clamp-top-10-cac1571e/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)