Schema Name Normalizer

Overview

You send a JSON Schema or a plain JSON object and pick a convention — camelCase, PascalCase, snake_case, or kebab-case — and we rename the fields to match. You get the rewritten document plus a mapping that lists every field's old and new name, so the rename stays reversible and reviewable. In schema mode we only touch property names, keeping keywords, $ref targets, and definition names exactly as you wrote them. If two different names collapse into one, we tell you rather than quietly losing a field.

A document that mixes user_id, userName, and User-Email breaks code generation and makes mapping layers miserable. Renaming by hand is tedious and easy to get subtly wrong, so we do it by rule and show you every change we made.

When to use it

Scope

Non-goals

• We never rename schema keywords such as type, items, required, $ref, or $defs
• We never rewrite the target of a $ref, so a rename can leave a reference stale
• We never check the document against a schema

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"schema.normalize_schema_names","input":{"input":{"type":"object","properties":{"user_id":{"type":"string"}}},"targetCase":"camelCase"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("schema.normalize_schema_names", {"input":{"type":"object","properties":{"user_id":{"type":"string"}}},"targetCase":"camelCase"});

Errors

Other limits

Limitations

• We never rename schema keywords such as type, items, required, $ref, or $defs
• We never rewrite the target of a $ref, so a rename can leave a reference stale
• We never check the document against a schema
• Renaming schema keywords or the names inside $defs
• Checking data against a schema (schema.validate_json)

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "schema.normalize_schema_names",
  "input": {
    "input": {
      "type": "object",
      "properties": {
        "user_id": {
          "type": "string"
        }
      }
    },
    "targetCase": "camelCase"
  }
}

Examples

{
  "input": {
    "type": "object",
    "properties": {
      "user_id": {
        "type": "string"
      }
    }
  },
  "targetCase": "camelCase"
}

{
  "transformed": {
    "type": "object",
    "properties": {
      "userId": {
        "type": "string"
      }
    }
  },
  "mappings": [
    {
      "path": "/properties/user_id",
      "normalized": "userId",
      "original": "user_id"
    }
  ],
  "collisions": []
}

{
  "targetCase": "PascalCase",
  "includeTransformed": false,
  "input": {
    "type": "object",
    "properties": {
      "user_name": {
        "type": "string"
      }
    }
  }
}

{
  "collisions": [],
  "mappings": [
    {
      "path": "/properties/user_name",
      "normalized": "UserName",
      "original": "user_name"
    }
  ]
}

Recommended use cases

• Line up payload keys with your language's conventions before you generate code
• Move a schema from snake_case to camelCase without hand-editing every property
• Produce the rename map a mapping or migration layer needs

Avoid for

• Renaming schema keywords or the names inside $defs
• Checking data against a schema (schema.validate_json)

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags