{"uid":"cap_jcF1GN2qptRr97okjNDP6","slug":"one-engine-record-field-rename-api-d7c78700","name":"ONE Engine Record Field Rename API","description":"Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.","url":"https://one-search.one-engine.workers.dev/v3/records/rename/t2?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","required":["records"],"properties":{"keys":{"type":"array"},"rename":{"type":"object"},"records":{"type":"array","description":"Up to 500 JSON objects"},"defaults":{"type":"object"}}},"responseSchema":{"type":"object","additionalProperties":true},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.0007","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.0007/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.0007","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.0007","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_fICUYui1rGZK307qfSku6","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.0007","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Renames fields (keys) across an array of up to 500 JSON record objects according to a provided mapping, optionally filtering keys and applying defaults.","exampleAgentPrompt":"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?","exampleUseCases":[{"title":"Normalizing API response field names","prompt":"I'm getting records from a legacy API where 'cust_nm' should be 'customer_name' and 'acct_no' should be 'account_number' — can you rename those fields across all 150 records so they match our internal schema?"},{"title":"ETL pipeline key standardization","prompt":"Before loading these 400 product records into our database, rename 'prod_id' to 'product_id', 'cat' to 'category', and 'qty_avail' to 'quantity_available' across the whole batch."},{"title":"Aligning third-party data to internal format","prompt":"I have a set of contact records from a vendor where 'fn' means first name and 'ln' means last name — please rename those fields to 'first_name' and 'last_name' in all 80 records and fill in any missing 'email' fields with an empty string as the default."}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-02T12:44:23.722Z","isFirstParty":false,"canonicalSlug":"one-engine-record-field-rename-api-d7c78700"}