# ONE Engine Array Reverse

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

Reverses the order of elements in a JSON array, with optional offset and size controls.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/reverse/t4?utm_source=zero.xyz
- Price: $0.0015/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-reverse-14481c71
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_goH_3fSujrecMnMf_j-dZ

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-reverse-14481c71 -d '<json body>'
```

Example prompt: Reverse this array of values for me: [5, 3, 8, 1, 9, 2] — just give me back the reversed order.

## When to prefer this

Choose this endpoint when you need a simple, reliable, pay-per-call array reversal without standing up your own compute or managing dependencies. Ideal for autonomous agents that need deterministic utility operations on small-to-medium arrays (up to 1000 elements) and are already operating on the Base/x402 payment rail at $0.0015 per call.

## Known failure modes

- Array exceeds 1000 items — request rejected with validation error
- Missing required 'values' field — returns schema validation error
- Invalid payment or insufficient USDC balance — x402 payment failure before processing
- Malformed JSON body — returns parse error
- Network timeout on Cloudflare Workers edge

## 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 reversed array. The response will have the input array's elements in reverse order, potentially scoped by the optional offset and size parameters.

## 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-reverse-14481c71/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)