Schema-Guided JSON Repair

Overview

You send a document that already parses, the schema it violates, and the exact list of repairs we may perform. We apply only those, revalidate, and return the repaired document together with the RFC 6902 patch that produced it, so every edit to your data can be reviewed, replayed or rejected. Where a violation admits two authorised repairs we apply neither and name both: guessing between them would be invention wearing a repair's name. schema.repair_json fixes what stops a document parsing; this skill starts where that one stops.

Agents and hand-written fixtures produce documents that are one string quote away from valid. Fixing those by hand is tedious; fixing them with an unbounded coercion library is how a "0" becomes false and a bug ships. An allowlist the caller writes, plus a patch the caller can read, is the only version of this that is safe to run over someone else's data.

When to use it

Scope

Non-goals

• We never invent a business value; the one exception is a schema-declared default you explicitly authorise
• We never choose between two authorised repairs — both are named and neither runs
• We never fix a document that does not parse; schema.repair_json does that
• We never truncate meaning: only leading or trailing whitespace is ever cut
• We never report a repair we did not revalidate

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.repair_json_to_schema","input":{"text":"{\"count\":\"17\"}","schema":{"type":"object","properties":{"count":{"type":"integer"}}},"repairPolicy":{"allow":["COERCE_STRING_TO_INTEGER"]}}}'

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

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

const { output } = await sq.execute("schema.repair_json_to_schema", {"text":"{\"count\":\"17\"}","schema":{"type":"object","properties":{"count":{"type":"integer"}}},"repairPolicy":{"allow":["COERCE_STRING_TO_INTEGER"]}});

Errors

Other limits

Limitations

• We never invent a business value; the one exception is a schema-declared default you explicitly authorise
• We never choose between two authorised repairs — both are named and neither runs
• We never fix a document that does not parse; schema.repair_json does that
• We never truncate meaning: only leading or trailing whitespace is ever cut
• We never report a repair we did not revalidate
• Fixing JSON that does not parse, which schema.repair_json does
• Filling in missing business data, which nothing here will do

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "schema.repair_json_to_schema",
  "input": {
    "text": "{\"count\":\"17\"}",
    "schema": {
      "type": "object",
      "properties": {
        "count": {
          "type": "integer"
        }
      }
    },
    "repairPolicy": {
      "allow": [
        "COERCE_STRING_TO_INTEGER"
      ]
    }
  }
}

Examples

{
  "text": "{\"count\":\"17\"}",
  "schema": {
    "type": "object",
    "properties": {
      "count": {
        "type": "integer"
      }
    }
  },
  "repairPolicy": {
    "allow": [
      "COERCE_STRING_TO_INTEGER"
    ]
  }
}

{
  "repairs": [
    {
      "pointer": "/count",
      "repair": "COERCE_STRING_TO_INTEGER",
      "keyword": "type",
      "schemaPointer": "/properties/count/type",
      "fromType": "string",
      "toType": "integer"
    }
  ],
  "unresolved": [],
  "valid": true,
  "json": {
    "count": 17
  },
  "summary": {
    "violationCount": 1,
    "repairCount": 1,
    "unresolvedCount": 0,
    "validationPasses": 2,
    "draft": "https://json-schema.org/draft/2020-12/schema",
    "changed": true,
    "truncated": false
  },
  "errors": [],
  "patch": [
    {
      "op": "replace",
      "path": "/count",
      "value": 17
    }
  ]
}

{
  "text": "{\"count\":17}",
  "schema": {
    "type": "object",
    "properties": {
      "count": {
        "type": "integer"
      }
    }
  },
  "repairPolicy": {
    "allow": [
      "COERCE_STRING_TO_INTEGER"
    ]
  }
}

{
  "repairs": [],
  "unresolved": [],
  "valid": true,
  "json": {
    "count": 17
  },
  "summary": {
    "violationCount": 0,
    "repairCount": 0,
    "unresolvedCount": 0,
    "validationPasses": 1,
    "draft": "https://json-schema.org/draft/2020-12/schema",
    "changed": false,
    "truncated": false
  },
  "errors": [],
  "patch": []
}

Recommended use cases

• Coerce an agent's stringified numbers and booleans into a typed payload
• Bring a hand-written fixture up to its schema with an auditable patch
• Decide whether a rejected payload is mechanically fixable at all

Avoid for

• Fixing JSON that does not parse, which schema.repair_json does
• Filling in missing business data, which nothing here will do

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