# ONE Engine Records Rename

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

Renames keys within an array of JSON records according to a field mapping, with optional key filtering and default values.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/records/rename/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-rename-b849e031
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cgh_bvWQi0K-q-PH_6VVz

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-rename-b849e031 -d '<json body>'
```

Example prompt: I have a batch of up to 500 JSON records where I need to rename the field 'user_id' to 'userId' and 'first_name' to 'firstName' — can you run those records through the ONE Engine rename utility and give me the updated list?

## When to prefer this

Choose this endpoint when you need a cheap, stateless, pay-per-call utility to batch-rename fields across up to 500 JSON records without standing up your own transformation infrastructure. Ideal for lightweight ETL, schema normalization between services, or quick field remapping in an agentic pipeline where spinning up a full data-processing service is overkill.

## Known failure modes

- Missing required 'records' field returns validation error
- Records array exceeding 500 items may be rejected or truncated
- Invalid rename mapping (non-string keys or values) may cause transformation errors
- Payment failure via x402 protocol results in 402 response before processing
- Malformed JSON in records array causes parse errors

## How this service works

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

## Output

An object containing the input records with keys renamed according to the provided mapping. Fields not listed in the rename map are passed through unchanged; optional key filtering retains only specified keys; defaults are applied where values are missing.

## 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-rename-b849e031/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)