# ONE Engine Records Pick T1

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

Selects and reshapes up to 500 JSON records by picking specific keys, renaming fields, and applying defaults.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/pick/t1?utm_source=zero.xyz
- Price: $0.0005/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-t1-9ab20519
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f1Uw_AHh-2lEt4TeA2XgS

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-t1-9ab20519 -d '<json body>'
```

Example prompt: I have a batch of up to 500 JSON objects and I only want to keep the 'id', 'name', and 'email' fields — rename 'name' to 'fullName', and set 'email' to 'unknown@example.com' if it's missing.

## When to prefer this

Choose this endpoint when you need a lightweight, cheap ($0.0005 USDC) pay-per-call operation to project, rename, or apply defaults to a batch of JSON records without spinning up a full data pipeline or ETL service. Ideal for autonomous agents doing quick record normalization inline.

## Known failure modes

- Empty or missing 'records' array causes a validation error
- Exceeding 500 records may result in truncation or rejection
- Invalid JSON structure in records causes parse errors
- Payment failure (HTTP 402) if x402 payment is not provided or insufficient
- Keys referencing non-existent fields are silently omitted from output

## How this service works

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

## Output

Returns a JSON object or array of the transformed records, each containing only the picked and/or renamed fields with any specified defaults applied to missing values.

## 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-t1-9ab20519/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)