# ONE Engine Array Chunk

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

Splits a JSON array into a chunk of items at a given offset and size, optionally compared against another array.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/chunk/t6?utm_source=zero.xyz
- Price: $0.004/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-array-chunk-c1111e23
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1oEkTXJrW_yRIXJVBN_kx

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-c1111e23 -d '<json body>'
```

Example prompt: Take this array of 200 product IDs and give me a chunk of 25 items starting at offset 50.

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call array chunking/slicing operation without standing up server-side logic — especially in autonomous agent pipelines on Base that already use x402 micropayments. Ideal for paginating through large arrays on-the-fly or extracting fixed-size windows from a dataset.

## Known failure modes

- Missing required 'values' array returns a validation error
- Array exceeds 1000-item limit returns rejection
- Non-integer offset or size may cause unexpected behavior
- Empty array returns empty chunk
- Offset beyond array length returns empty result
- Payment failure via x402 returns 402 status

## How this service works

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

## Output

Returns an object containing the sliced/chunked portion of the input array based on the specified offset and size, with optional comparison results if a second array is 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-c1111e23/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)