# ONE Engine Array Unique (T3)

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

Returns only the unique elements from a JSON array, optionally comparing against a second array and supporting offset/size pagination.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/unique/t3?utm_source=zero.xyz
- Price: $0.001/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-unique-t3-b89d84a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1zJBfa3kNkNSBMrMr3od6

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-unique-t3-b89d84a9 -d '<json body>'
```

Example prompt: I have this list of product IDs and some of them are repeated — can you deduplicate it and return only the unique values? Here's the array: [101, 202, 101, 303, 202, 404].

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call deduplication operation on a JSON array of up to 1000 items, especially within an autonomous agent pipeline running on Base via x402 micropayments. Ideal when you want set-difference behavior (unique relative to a comparison array) or paginated unique results without standing up your own data processing infrastructure.

## Known failure modes

- Array exceeds 1000-item limit — request rejected
- Malformed JSON array in values field — validation error
- Invalid offset or size values — parameter error
- Payment failure via x402 protocol — 402 response blocking execution

## How this service works

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

## Output

A JSON object containing the array of unique elements derived from the input values array, after removing duplicates and optionally filtering against a comparison array, with pagination applied if size/offset were specified.

## 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-unique-t3-b89d84a9/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)
