# ONE Engine Records Defaults Transformer (T1)

> ONE Engine Records Defaults Transformer (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).

Applies default field values to a batch of up to 500 JSON records, optionally filtering keys and renaming fields.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/defaults/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-defaults-transformer-t1-89886c8b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_p3mp4Zv7EGkWLHXb-i6CV

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-defaults-transformer-t1-89886c8b -d '<json body>'
```

Example prompt: I have 200 JSON records where some fields like 'status' and 'priority' are missing — can you apply defaults of status='pending' and priority=1 to all of them, and also rename the 'uid' field to 'id'?

## When to prefer this

Choose this endpoint when you need a cheap, pay-per-call batch transformation of JSON records — specifically for applying defaults, renaming fields, or filtering keys across up to 500 objects in a single call. It is ideal for autonomous agent pipelines on Base where micro-payments via x402 are acceptable and you want a lightweight utility without standing up your own data processing infrastructure.

## Known failure modes

- Exceeding 500 records limit returns an error
- Malformed JSON in the records array causes a 400-level error
- Missing required 'records' field returns a validation error
- Payment failure via x402 returns a 402 Payment Required response
- Invalid rename map (non-object) causes schema validation failure

## 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 with default values merged into records where fields were absent, keys filtered to only those requested, and field names renamed according to the provided map. The response is an object containing 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-defaults-transformer-t1-89886c8b/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)