# ONE Engine Array Intersection

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

Computes the intersection of two arrays, returning shared elements and their count.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v1/array/intersection?utm_source=zero.xyz
- Price: $0.0011/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-20fbd755
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J-HsfslBQvQWpoSENkcxV

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-20fbd755 -d '<json body>'
```

Example prompt: Find the common elements between these two lists: [1, 2, 3, 4, 5] and [2, 3, 6, 7] — give me the shared values and how many there are.

## When to prefer this

Use this endpoint when you need a quick, low-cost programmatic intersection of two arrays without spinning up local compute or a database query. Ideal for autonomous agents that need set overlap on the fly and want to pay per call rather than maintain infrastructure. Best for small-to-medium arrays where a simple shared-element computation suffices.

## Known failure modes

- Missing one or both arrays returns a validation error
- Non-array input types cause schema mismatch errors
- Empty arrays on either side return count 0 and empty values
- Payment failure via x402 returns HTTP 402 and the call is not processed

## How this service works

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

## Output

A JSON object with a 'count' integer indicating how many elements are shared between the two input arrays, and a 'values' array listing those shared elements.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "a": {
   "type": "array"
  },
  "b": {
   "type": "array"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 2,
  "values": [
   2,
   3
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-array-intersection-20fbd755/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)