Back to Browse
KiHustle JSON Key Rename API
x402
KiHustle JSON Key Rename API is a paid API for AI agents from kihustle.tech, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-13).
Renames keys in a JSON object according to a provided field mapping, returning the transformed object with new key names.
Price / call$0.002
Success—
StatusUnknown
How this service works
Kostenlose Guides, Solo-Playbooks und Artikel zu KI, Automation und Side Hustles — für Menschen, die mit echten Systemen online Einkommen aufbauen wollen. Transparent finanziert über faire Affiliate-Links.
Output
Returns a JSON object with the same values as the input but with keys renamed according to the provided mapping. The response includes a 'result' field containing the transformed object and a 'status' field confirming success.
Example use cases
Normalize API response field names
“I'm getting a response from a third-party API with fields like 'usr_nm' and 'acct_id' — can you rename them to 'username' and 'accountId' in this JSON object so I can pass it to my database?”
Convert camelCase to snake_case keys
“Take this JSON object with camelCase keys like 'createdAt', 'userId', and 'orderTotal' and rename them to 'created_at', 'user_id', and 'order_total' for my Python backend.”
Adapt data for a different schema
“I need to reformat this JSON payload before sending it to a webhook — rename 'name' to 'full_name', 'phone' to 'phone_number', and 'city' to 'location_city': {"name": "John", "phone": "555-1234", "city": "Berlin"}.”
Technical details
Endpoint
POSThttps://kihustle.tech/bot-bazaar/api/v1/json-key-rename?utm_source=zero.xyzWhen to prefer
Use this endpoint when you need a lightweight, stateless key-rename operation on a JSON object without deploying custom transformation logic. Ideal for agent pipelines that need to normalize field names between APIs, adapt payloads to a target schema, or convert naming conventions (e.g. camelCase to snake_case) on the fly at low cost ($0.002 per call).
Side effects
- Missing 'data' or 'mapping' fields in the request body — returns error
- Mapping references keys not present in the data object — those keys are silently skipped or cause partial transformation
- Malformed JSON in either field — returns parse error
- Circular or conflicting key mappings — undefined behavior
- Empty mapping object — returns original object unchanged
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| data | object | |
| mapping | object |
Output
Schema · Response
{
"type": "json",
"example": {
"result": "processed",
"status": "success"
}
}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"