# ONE Engine Array Intersection (t2)

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

Computes the intersection of two arrays, returning elements present in both input arrays.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/array/intersection/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-intersection-t2-e0ffe8ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_roOEdlMEeemfbeBdL3SYN

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

Example prompt: Find the common elements between these two arrays for me: [1, 2, 3, 4, 5] and [3, 4, 5, 6, 7] — return whatever values appear in both.

## When to prefer this

Choose this endpoint when you need a fast, cheap, pay-per-call set intersection on two arrays of up to 1000 items each, without provisioning any infrastructure. Ideal for AI agents that need on-demand utility computation billed in micro-USDC via x402 on Base, particularly when you don't want to run custom code or maintain a backend service.

## Known failure modes

- Missing required `values` field returns validation error
- Arrays exceeding 1000 items rejected
- Malformed JSON arrays cause parsing errors
- Payment failure (x402) blocks execution
- Empty intersection returns empty array (not an error)

## 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 array of elements found in both the primary `values` array and the `other` comparison array, representing the computed set intersection.

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