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

Splits a JSON array into fixed-size chunks, optionally starting at an offset, for downstream agent processing.

## Facts

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

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

Example prompt: Split this list of 200 product IDs into chunks of 25 so I can process them in parallel batches.

## When to prefer this

Use this endpoint when an AI agent needs to split a large array into fixed-size batches for parallel processing, pagination, or rate-limited downstream API calls. Prefer it over manual chunking logic when operating inside an agent workflow that already uses x402 micropayments on Base, making it a cheap ($0.0065 USDC) drop-in utility step.

## Known failure modes

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

## How this service works

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

## Output

An object containing the original array partitioned into sub-arrays (chunks) of the specified size. Each chunk is an array of consecutive elements from the input. If an offset is provided, chunking begins at that index. An optional comparison array can be supplied for differential operations.

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