Required Fields Checker

Overview

You send a JSON payload plus the paths that must carry a value — as JSON Pointers, dotted paths, or a JSON Schema whose nested required lists we walk for you. We tell you whether the payload is complete and, for every gap, the exact path and why it counts as missing (absent, null, or empty_string). We look at presence only, never at types or formats, so use schema.validate_json when you need full conformance.

Rejected requests usually come down to one empty nested field, and a full schema validation run buries that answer in type noise. You get the gap list straight away.

When to use it

Scope

Non-goals

• We never check value types — reach for schema.validate_json
• We never check enum membership — reach for schema.validate_enum_values
• We never repair, fill in, or transform your payload

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.check_required_fields","input":{"payload":{"orderId":"SO-88120","shipTo":{"city":"Antwerp"}},"requiredPaths":["/orderId","/shipTo/city","/shipTo/postalCode"]}}'

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

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

const { output } = await sq.execute("schema.check_required_fields", {"payload":{"user":{"name":"Alice Moreau"}},"requiredPaths":["/user/name","/user/email"]});

Errors

Other limits

Limitations

• We never check value types — reach for schema.validate_json
• We never check enum membership — reach for schema.validate_enum_values
• We never repair, fill in, or transform your payload
• Full schema conformance, where types and formats matter (schema.validate_json)
• Checking that a value is one of an allowed set (schema.validate_enum_values)
• Comparing two payloads against each other

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "schema.check_required_fields",
  "input": {
    "payload": {
      "user": {
        "name": "Alice Moreau"
      }
    },
    "requiredPaths": [
      "/user/name",
      "/user/email"
    ]
  }
}

Examples

{
  "payload": {
    "user": {
      "name": "Alice Moreau"
    }
  },
  "requiredPaths": [
    "/user/name",
    "/user/email"
  ]
}

{
  "missing": [
    {
      "reason": "absent",
      "path": "/user/email"
    }
  ],
  "complete": false,
  "checkedCount": 2
}

{
  "payload": {
    "invoiceNumber": "INV-2026-0042",
    "customer": {
      "email": "[email protected]"
    }
  },
  "schema": {
    "required": [
      "invoiceNumber",
      "customer"
    ],
    "type": "object",
    "properties": {
      "customer": {
        "type": "object",
        "required": [
          "email"
        ]
      }
    }
  }
}

{
  "missing": [],
  "complete": true,
  "checkedCount": 3
}

Recommended use cases

• Preflight a request body before you post it to a strict partner API
• Confirm an agent-assembled payload carries every mandatory field
• Tell a caller exactly which nested field is still empty, by pointer

Avoid for

• Full schema conformance, where types and formats matter (schema.validate_json)
• Checking that a value is one of an allowed set (schema.validate_enum_values)
• Comparing two payloads against each other

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