Back to Browse
Delx Commerce — JSON Object Rename Keys
x402
Delx Commerce — JSON Object Rename Keys is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).
Renames the keys of a JSON object according to a provided key mapping, returning the transformed object with collision tracking.
Price / call$0.001
Success—
StatusUnknown
How this service works
Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.
Output
Returns the input object with keys renamed according to the mapping, a list of any key collisions that occurred during renaming, a status field ('pass'), an evidence block confirming no data retention and including the SHA256 hash of the input, and a schema identifier for the operation.
Example use cases
API response schema normalization
“I'm getting a response from a third-party API with snake_case keys like 'user_id' and 'created_at', but my system expects camelCase. Can you rename all the keys in this object: {"user_id": 42, "created_at": "2024-01-01"} — map 'user_id' to 'userId' and 'created_at' to 'createdAt'?”
Database field name migration
“I have a record from our old database schema that uses abbreviations: {"usr_nm": "ada", "acct_no": "123", "bal": 500.0}. Rename those keys to their full names — 'usr_nm' to 'username', 'acct_no' to 'accountNumber', and 'bal' to 'balance'.”
Frontend data shape alignment
“Our backend returns {"colour": "blue", "centre": "NYC", "organisation": "ACME"} but our frontend expects American English spellings. Rename 'colour' to 'color', 'centre' to 'center', and 'organisation' to 'organization' in that object.”
Technical details
Endpoint
POSThttps://commerce.delx.ai/api/v1/x402/json-object-rename-keys?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you need a lightweight, verifiable, pay-per-use key renaming operation on a JSON object without signing up for a service or managing API keys. Ideal for AI agents that need to normalize field names between schemas on the fly, especially when auditability (SHA256 evidence, no-retention guarantee) matters. Prefer over custom code when operating in a stateless agent pipeline that already uses USDC/x402 micropayments.
Side effects
- Object or mapping exceeds 128 properties — request rejected
- Invalid JSON structure in object or mapping fields — parse error
- Key collision when two source keys map to the same target key — reported in collisions array
- Payment failure or insufficient USDC balance — 402 response before processing
- Malformed request body — missing required fields returns error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| object | object | Object supplied to JSON Object Rename Keys; used only for this bounded calculation and processed in memory without retention. |
| mapping | object | Mapping supplied to JSON Object Rename Keys; used only for this bounded calculation and processed in memory without retention. |
Output
Schema · Response
{
"type": "json",
"example": {
"result": {
"object": {
"id": 1,
"firstName": "Ada"
},
"collisions": []
},
"schema": "delx/util-json-object-rename-keys/v1",
"status": "pass",
"evidence": {
"retained": false,
"input_sha256": "17b6ed7c6acbd73e4c278919af805585c725f614019bd98fd34297fddb0367ca",
"external_calls": 0
},
"operation": "data_batch:json_object_rename_keys"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"