{"uid":"cap_GHjQM0rd2uZZgv0vtw1g6","slug":"g-forge-rename-json-fields-67b60c53","name":"G-Forge Rename JSON Fields","description":"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.","url":"https://api.getretold.com/services/agent-auto-launch-rename/invoke?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"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}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_NHz2YRIFKDwP8O9PU4mb2","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"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.","exampleAgentPrompt":"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?","exampleUseCases":[{"title":"Bridge CRM and billing system schemas","prompt":"My CRM exports records with 'firstName' and 'lastName' but the billing API requires 'first_name' and 'last_name' — rename those fields in all 500 records so I can pass them straight through."},{"title":"Normalize third-party API response before storage","prompt":"I'm getting records from a vendor API where the ID field is 'recordId' and the timestamp is 'createdAt', but my database schema uses 'id' and 'created_at' — can you remap those top-level keys across all the records?"},{"title":"Align analytics export with dashboard schema","prompt":"I have a JSON export from our analytics tool where revenue is labeled 'rev' and the date column is 'dt', but the dashboard expects 'revenue' and 'date' — rename those fields in the 300 records so the dashboard can read them correctly."}],"resultDescription":"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.","failureModes":["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)"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-24T12:34:42.260Z","isFirstParty":false,"canonicalSlug":"g-forge-rename-json-fields-67b60c53"}