Use this text operation when its stated character encoding, token boundaries, normalization, case handling, and output format match the surrounding workflow.

Document A

Required string. Starting JSON document.

Document B

Required string. Target JSON document.

The cited overview of JSON supplies background for the terminology and domain context used by this tool.^[1]

Produce a minimal deterministic RFC 6902-style add/remove/replace patch turning one JSON document into another. Inputs are interpreted exactly in the displayed units and the calculation returns the following fields without presentation rounding.

Patch

Returned string. Serialized array of add/remove/replace operations with RFC 6901 pointers.

Operation count

Returned integer. Number of operations in the patch.

• Unicode normalization, locale, grapheme clusters, malformed input, ambiguous syntax, and implementation-specific conventions can change text-processing results.
• Use finite inputs in the displayed units, preserve source measurements and assumptions, and independently verify consequential decisions.

Preserve the original text, test representative non-ASCII and malformed cases, and use a standards-aware parser or serializer when interoperability matters.

• JSON Patch Applier

  Apply a minimal RFC 6902-style add/remove/replace patch with RFC 6901 pointers to a JSON document.

• JSON Pointer Resolver

  Resolve an RFC 6901 JSON Pointer against a document and report the located value.

• JSON Flatten

  Flatten a JSON object into single-level dot-path keys pointing at primitive leaves.