# ONE Engine Array Flatten (T1)

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

Flattens a nested JSON array into a single-level array, with optional comparison against another array.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/flatten/t1?utm_source=zero.xyz
- Price: $0.0005/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-flatten-t1-550712d2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jV9Et_zotfeX58Icnr8c-

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-flatten-t1-550712d2 -d '<json body>'
```

Example prompt: Flatten this nested array for me: [[1, 2], [3, [4, 5]], 6] — I need it as a single flat list.

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call array flattening operation without spinning up a local compute environment — especially in autonomous agent pipelines on Base using x402 micropayments where you want predictable, low-cost ($0.0005 USDC) data normalization at the edge.

## Known failure modes

- Input array exceeds 1000 items — request rejected
- Malformed or non-array 'values' field — validation error
- Payment not included or insufficient — 402 Payment Required response
- Network timeout on the Cloudflare Worker edge
- Invalid 'offset' or 'size' parameter types causing schema rejection

## 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 flattened (single-level) version of the input array, potentially with comparison results if an optional 'other' array was supplied.

## 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-flatten-t1-550712d2/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)