# ONE Engine Records Pick T8

> ONE Engine Records Pick T8 is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.01/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/t8?utm_source=zero.xyz
- Price: $0.01/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-t8-9ea47287
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MBJc7wpDfFHwPDxQpbTdG

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-t8-9ea47287 -d '<json body>'
```

Example prompt: I have an array of up to 500 customer JSON objects and I only want to keep the 'id', 'name', and 'email' fields — can you pick just those keys, rename 'name' to 'fullName', and set a default of 'unknown' for any missing email?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call JSON record projection and field-renaming step within an agent pipeline — especially useful when you want to slim down large API responses, normalize field names across heterogeneous sources, or apply default values before passing data downstream, all without spinning up your own ETL infrastructure.

## Known failure modes

- Records array exceeds 500 items — request rejected or truncated
- Malformed JSON input causes parsing error
- Missing required 'records' field returns validation error
- Payment via x402 on Base fails or is rejected — 402 response returned
- Rename mapping references keys not present in records — silently skipped or empty output
- Network timeout on Cloudflare Worker edge

## 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 transformed array of records, where each record has been filtered to the requested keys, fields renamed according to the mapping, and missing fields filled with provided defaults.

## 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-t8-9ea47287/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)