# ONE Engine Array Chunk (Top 10)

> ONE Engine Array Chunk (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-16).

Splits a JSON array into chunks and returns the top 10 chunk at a specified offset, optionally compared against another array.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/chunk/t10?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-array-chunk-top-10-9236cb2c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dslKJBzke8nL-9hDHP_SZ

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-array-chunk-top-10-9236cb2c -d '<json body>'
```

Example prompt: Split this list of 500 product IDs into chunks of 50 and give me the top 10 items starting at offset 100: [list of IDs].

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call array chunking operation within an autonomous agent pipeline on Base using x402 micropayments. Ideal for agents that need to paginate or partition arrays without standing up custom infrastructure.

## Known failure modes

- Input array exceeds 1000 items — request rejected
- Missing required 'values' field — validation error
- Non-integer size or offset — schema validation failure
- Payment not completed via x402 — 402 Payment Required response
- Empty array input — may return empty chunk

## 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 items from the chunked array at the specified offset, with optional comparison results if a second array was provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "values"
 ],
 "properties": {
  "size": {
   "type": "integer"
  },
  "other": {
   "type": "array",
   "description": "Optional comparison array"
  },
  "offset": {
   "type": "integer"
  },
  "values": {
   "type": "array",
   "description": "JSON array with at most 1000 items"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-array-chunk-top-10-9236cb2c/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)