# ONE Engine Record Field Rename API

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

Renames fields (keys) across an array of up to 500 JSON record objects according to a provided mapping, optionally filtering keys and applying defaults.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/rename/t2?utm_source=zero.xyz
- Price: $0.0007/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-record-field-rename-api-d7c78700
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jcF1GN2qptRr97okjNDP6

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-record-field-rename-api-d7c78700 -d '<json body>'
```

Example prompt: I have 200 JSON records where the field is called 'usr_id' but I need it renamed to 'user_id', and 'ts' renamed to 'timestamp' — can you run them through the ONE Engine rename endpoint to get back the corrected records?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call solution to bulk-rename fields across up to 500 JSON records without standing up your own transformation infrastructure. It is ideal for AI agents doing on-the-fly ETL normalization, schema alignment between APIs, or data pipeline preprocessing steps where field naming consistency matters and cost per call must stay minimal.

## Known failure modes

- Exceeding the 500-record limit causes rejection or partial processing
- Invalid or non-object entries in the records array may cause errors
- Rename mapping referencing non-existent fields is silently ignored (no-op)
- Malformed JSON in request body returns a 4xx error
- Payment failure via x402 returns 402 Payment Required

## 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 records with all specified field renames applied, unwanted keys filtered out (if a key list was provided), and default values filled in for any missing fields.

## 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-record-field-rename-api-d7c78700/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)