# ONE Engine Array Chunk (t2)

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

Splits a JSON array into fixed-size chunks, optionally offset or compared against another array, returning the chunked result.

## Facts

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

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

Example prompt: Can you split this list of 200 product IDs into chunks of 25 so I can process them in parallel batches? Here's the array: [1, 2, 3, ...]

## When to prefer this

Choose this endpoint when you need a simple, low-cost ($0.0007 USDC) pay-per-call utility to chunk or paginate a JSON array on Base via x402 protocol, especially in autonomous agent pipelines where you need reliable batch splitting without spinning up custom infrastructure. Best suited for arrays up to 1000 items.

## Known failure modes

- Array exceeds 1000-item limit — request rejected
- Missing required 'values' field — validation error
- Non-integer size or offset — invalid input error
- Payment not provided or insufficient — 402 Payment Required
- Empty array input — may return empty chunks or error

## How this service works

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

## Output

Returns an object containing the original array partitioned into sub-arrays of the specified chunk size. If an offset is provided, chunking begins from that position. If a comparison array is provided, the result may include comparison data alongside each chunk.

## 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-t2-7e92002f/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)