#json-patch

Address values inside a JSON document by JSON Pointer (RFC 6901) — the /a/b/0 path syntax used by JSON Patch (RFC 6902), JSON Schema and OpenAPI $ref. The get endpoint resolves the value at a pointer (and tells you whether it exists); set writes a value at a pointer and returns the modified document (use - as the final array token to append); and list enumerates every pointer in a document, optionally only the leaf values. Token escaping (~0 for ~, ~1 for /) is handled for you. Perfect for surgically reading and patching deep JSON, building config and form tooling, and walking API responses. Pure local computation — no key, no third-party service, instant; up to 2 MB via POST. Live, nothing stored. 4 endpoints. Distinct from JSONPath querying, JSON diff/patch and dot-notation flattening.

api.oanor.com/jsonpointer-api

Compare and patch JSON documents to RFC standards. Pass two documents and the service returns whether they are equal, an RFC 6902 JSON Patch (the precise add/remove/replace operations that turn the first into the second, using RFC 6901 JSON-Pointer paths), a change summary, and an RFC 7386 JSON Merge Patch. The patch endpoint goes the other way: apply an RFC 6902 patch (add, remove, replace, move, copy and test operations) or an RFC 7386 merge patch to a document and get the result. Documents can be sent inline or as a JSON body. Everything is computed locally with no network calls, so it is fast and deterministic. Built for configuration and state management, API change detection, audit trails and change logs, optimistic-concurrency checks and data-sync pipelines. A JSON diff/patch engine — distinct from text diffing (textdiff), JSONPath querying (jsonpath), JSON validation and pretty-printing (json) and JSON-Schema validation (jsonschema). No upstream key, no cache.

api.oanor.com/jsondiff-api