# G-Forge Rename JSON Fields

> G-Forge Rename JSON Fields is a paid API for AI agents from api.getretold.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-24).

Renames top-level JSON keys in a batch of records using an explicit old-to-new field name mapping, preserving values, unmapped keys, and row order.

## Facts

- Endpoint: POST https://api.getretold.com/services/agent-auto-launch-rename/invoke?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/g-forge-rename-json-fields-67b60c53
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GHjQM0rd2uZZgv0vtw1g6

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 g-forge-rename-json-fields-67b60c53 -d '<json body>'
```

Example prompt: I have 200 JSON records from one API where the user ID field is called 'uid' and the email field is called 'emailAddress', but the next system expects 'user_id' and 'email' — can you rename those fields across all the records without touching anything else?

## When to prefer this

Choose this endpoint when you need to rename top-level JSON field names in bulk across many records without modifying values or structure. It is ideal for bridging two APIs or systems that use different naming conventions, normalizing exports before storage, or preparing records for a downstream service that expects specific field names. Prefer it over general-purpose ETL tools when you need a lightweight, stateless, single-step rename operation with explicit collision safety guarantees.

## Known failure modes

- Key collision: a target key name already exists in a record — request rejected
- Mapping exceeds 32 entries — validation error
- Input array exceeds 5000 rows — validation error
- Empty mapping (no entries) — validation error
- Malformed JSON in request body — parse error
- Old key in mapping not present in any record — silently skipped (no rename, no error)

## How this service works

Match one API's field names to another without rewriting the records. Rename top-level JSON keys using an explicit old-to-new mapping. Values, unmapped keys and row order are preserved; key collisions are rejected. Useful for connecting systems with different naming conventions.

## Output

An array of JSON records identical to the input except that top-level keys listed in the mapping have been renamed to their new names. Values, unmapped keys, and row order are fully preserved. If a key collision would occur (a new name already exists as another key), the call is rejected with an error.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "object",
   "required": [
    "rows",
    "mapping"
   ],
   "properties": {
    "rows": {
     "type": "array",
     "items": {
      "type": "object"
     },
     "maxItems": 5000
    },
    "mapping": {
     "type": "object",
     "maxProperties": 32,
     "minProperties": 1,
     "additionalProperties": {
      "type": "string"
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/g-forge-rename-json-fields-67b60c53/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.getretold.com](https://www.zero.xyz/host/api.getretold.com/llms.txt)