# 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.01/call, status unknown (last checked 2026-10-02).

Renames fields (keys) across an array of JSON record objects according to a provided mapping, with optional key filtering and default values.

## Facts

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

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-639db92e -d '<json body>'
```

Example prompt: I have a batch of up to 500 JSON records where the field is called 'user_id' but I need it renamed to 'userId', and 'ts' renamed to 'timestamp' — can you run them through the rename transformer?

## When to prefer this

Choose this endpoint when you need a cheap ($0.01 USDC), stateless, pay-per-call way to rename, filter, and set defaults on up to 500 JSON records in a single call — especially in autonomous agent workflows on Base where x402 micropayments are already supported. Prefer this over in-agent code execution when you want a hosted, auditable transformation step without spinning up compute.

## Known failure modes

- Missing required 'records' array returns validation error
- Records array exceeding 500 objects may be rejected or truncated
- Invalid rename mapping (non-object value) causes schema error
- Malformed JSON in records triggers parse error
- Payment not fulfilled via x402 results in 402 Payment Required response
- Empty records array returns empty result set

## 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 fields renamed according to the provided mapping. Keys not included in the rename map remain unchanged or are filtered based on the keys parameter. Default values are applied where specified.

## 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-639db92e/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)