# ONE Engine Array Rotate

> ONE Engine Array Rotate 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).

Rotates the elements of a JSON array by a given offset, optionally comparing against a second array.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/rotate/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-rotate-3e0400f0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aak5LFEX8mrDJY7H1Jaqo

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-rotate-3e0400f0 -d '<json body>'
```

Example prompt: Rotate this array ["a","b","c","d","e"] by 2 positions to the right.

## When to prefer this

Use this endpoint when you need a simple, cheap, stateless array rotation operation within an autonomous agent pipeline and don't want to run custom code. At $0.0005 per call it is ideal for high-frequency agent workflows that need reliable cyclic shifting of ordered lists without spinning up compute infrastructure.

## Known failure modes

- Missing required 'values' field returns an error
- Array exceeds 1000-item limit results in rejection
- Invalid offset type (non-integer) causes a validation error
- Payment failure (402) if x402 payment header is missing or insufficient
- Malformed JSON body returns a parse 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 rotated array with elements shifted by the specified offset, wrapping around cyclically. May also include comparison results if an optional second array was provided.

## 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-rotate-3e0400f0/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)