# ONE Engine Records Pick T4

> ONE Engine Records Pick 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).

Selects and reshapes specific fields from a batch of up to 500 JSON records, optionally renaming keys and applying defaults.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/pick/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-records-pick-t4-ac61f092
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OEGGhwTWbNBBQtm4dQR8e

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-records-pick-t4-ac61f092 -d '<json body>'
```

Example prompt: I have a batch of up to 500 product records and I only want to keep the 'id', 'name', and 'price' fields — also rename 'price' to 'cost' and default 'cost' to 0 if missing.

## When to prefer this

Use this endpoint when you need a cheap, pay-per-call utility to slim down, rename, or normalize fields across a batch of JSON records without spinning up your own data pipeline. Ideal for agents that frequently reshape API responses or ETL intermediate results at low cost ($0.0015 per call) with no infrastructure overhead.

## Known failure modes

- More than 500 records submitted — batch size limit exceeded
- Missing required 'records' field — validation error returned
- Invalid JSON structure in records array — parsing error
- Malformed rename map or defaults object — schema mismatch error
- Payment failure via x402 — 402 response before processing begins

## How this service works

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

## Output

Returns an array of transformed JSON objects where only the specified keys are retained, fields are renamed according to the rename map, and missing fields are filled with the provided defaults. The response is a JSON object with the processed records.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "records"
 ],
 "properties": {
  "keys": {
   "type": "array"
  },
  "rename": {
   "type": "object"
  },
  "records": {
   "type": "array",
   "description": "Up to 500 JSON objects"
  },
  "defaults": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-records-pick-t4-ac61f092/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)