# 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.001/call, status unknown (last checked 2026-10-02).

Splits a JSON array into fixed-size chunks, optionally offset and compared against another array

## Facts

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

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

Example prompt: Split this list of 500 product IDs into chunks of 50 items each, starting from offset 0: [array of IDs goes here].

## When to prefer this

Choose this endpoint when you need a simple, low-cost ($0.001 USDC) utility to split arrays into fixed-size partitions for pagination, batch processing, or parallel fan-out. Prefer it over implementing custom chunking logic when operating in an autonomous agent context on Base using x402 micropayments. Best for arrays up to 1000 items.

## Known failure modes

- Array exceeds 1000-item limit — request rejected
- Invalid or non-integer size/offset values — validation error
- Missing required 'values' field — 400 bad request
- Payment failure via x402 — 402 payment required before response is returned
- Empty array input may return empty chunks

## How this service works

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

## Output

Returns an object containing the input array partitioned into sub-arrays of the specified chunk size, starting at the given offset. If a comparison array is provided, results may include comparison metadata between the chunked segments and the other array.

## 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-bcbd45b9/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)