# ONE Engine Array Intersection (T4)

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

Computes the intersection of two arrays, returning elements present in both, with optional offset and size pagination controls.

## Facts

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

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-t4-8aa03d45 -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 just the first 10 results starting from offset 0.

## When to prefer this

Choose this endpoint when you need a quick, cheap, pay-per-call array intersection without spinning up your own set-logic computation — especially in agentic pipelines on Base where x402 micropayments are already supported. It supports pagination via size/offset, making it suitable for large result sets. Prefer it over in-memory set logic when the agent environment is stateless or when you want a consistent, hosted utility with predictable pricing.

## Known failure modes

- Missing required 'values' field returns a 400-level error
- Array exceeding 1000 items may be rejected or truncated
- Mismatched data types between arrays may yield empty intersection
- Payment not included or insufficient USDC triggers 402 Payment Required
- Malformed JSON input returns a parse 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 that appear in both the primary 'values' array and the optional 'other' comparison array. Results may be paginated using 'size' and 'offset' 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-intersection-t4-8aa03d45/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)