Assert JSON Equals

Overview

You give us the value you expected and the one you got, and we tell you exactly where they part company — one finding per spot, each with a JSON pointer you can read. You decide what counts as equal: whether key order matters, whether array order matters, how much numeric drift you tolerate, whether a null is the same as a missing key, which paths to skip entirely, and which paths only have to look like a UUID or a timestamp rather than match. Nothing is guessed and nothing is repaired, so the same pair always produces the same answer.

A test that asks a model whether two payloads look the same gives you a different answer on a bad day, and a plain equality check gives you "not equal" without telling you where.

When to use it

Scope

Non-goals

• Does not repair or reformat either value before comparing
• Does not check either value against a schema
• Does not judge whether two different values mean the same thing
• Does not coerce types the way JavaScript would, so 1 never equals "1"

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":"quality.assert_json_equals","input":{"expected":{"a":1},"actual":{"a":1}}}'

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

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

const { output } = await sq.execute("quality.assert_json_equals", {"actual":{"total":11},"expected":{"total":10}});

Errors

Other limits

Limitations

• Does not repair or reformat either value before comparing
• Does not check either value against a schema
• Does not judge whether two different values mean the same thing
• Does not coerce types the way JavaScript would, so 1 never equals "1"
• Fixing JSON that will not parse
• Checking a payload against a schema

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "quality.assert_json_equals",
  "input": {
    "actual": {
      "total": 11
    },
    "expected": {
      "total": 10
    }
  }
}

Examples

{
  "actual": {
    "total": 11
  },
  "expected": {
    "total": 10
  }
}

{
  "equal": false,
  "mismatches": [
    {
      "details": {
        "info": "difference=1"
      },
      "actual": 11,
      "path": "/total",
      "code": "VALUE_MISMATCH",
      "expected": 10
    }
  ],
  "summary": {
    "missing": 0,
    "unexpected": 0,
    "different": 1,
    "ignored": 0
  },
  "_meta": {
    "truncated": false,
    "comparisonProfile": "json-equality-1"
  }
}

{
  "actual": {
    "a": 1
  },
  "expected": {
    "a": 1
  }
}

{
  "equal": true,
  "mismatches": [],
  "summary": {
    "missing": 0,
    "unexpected": 0,
    "different": 0,
    "ignored": 0
  },
  "_meta": {
    "truncated": false,
    "comparisonProfile": "json-equality-1"
  }
}

Recommended use cases

• Check an API response matches what your test expects
• Compare two payloads while letting ids and timestamps vary
• Confirm a transformation changed only what it was meant to change

Avoid for

• Fixing JSON that will not parse
• Checking a payload against a schema

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