Choose a structural check, an explicit patch or a conservative repair according to the task. Inspect unsupported repair cases and conflict handling before committing a result.
No file editing, arbitrary JSON repair, semantic conflict resolution or guarantee that a structurally valid document is true.
Generate deterministic RFC 6902 add/remove/replace operations between supplied JSON values, with recursive object comparison, atomic arrays, escaped pointers and source/target digests. Does not infer moves or produce a minimal edit script.
Choose for: Generate JSON Patch from two document versions Find changed nested fields and produce machine-applicable operations
Outside this profile: Minimal array edit scripts, move detection, or arbitrary-precision JSON numbers Applying changes to remote files or APIs
Merge two supplied JSON document branches against an explicit base. Recursively merges object members, treats arrays atomically, distinguishes deletion from null, and returns no merged document when any conflict exists. Does not resolve semantic or textual conflicts.
Choose for: Merge independent JSON document edits against a common base Detect delete-versus-modify conflicts before combining agent results
Outside this profile: CRDT synchronization, line-based text merging or semantic conflict resolution Element-wise merging of arrays or applying partial conflict results
Atomically apply explicit nonoverlapping UTF-16 text edits after exact expected-slice and optional SHA-256 checks. Returns edited text, applied IDs and unchanged/replacement source mappings. Rejects split Unicode scalars and ambiguous insertion boundaries.
Choose for: Apply agent-proposed document edits with exact source assertions Produce source-to-result offset evidence for controlled text transformations
Outside this profile: Fuzzy matching, natural-language revision or edits to files on disk Mapping semantic annotations inside replacement text
Translate caller-supplied UTF-8 byte, UTF-16 code-unit or Unicode code-point offsets into all three coordinate systems and LF-based line/column positions. Only exact scalar boundaries are valid; text is never normalized or rewritten.
Choose for: Reconcile byte and character offsets from different extraction tools Convert annotation spans between UTF-8 UTF-16 and code-point systems
Outside this profile: Grapheme cluster, display-width, tokenizer or normalization mapping Offsets into binary files or malformed Unicode
Apply a single-file supplied unified diff to supplied LF text with exact old/new hunk positions, exact context matching, final-newline markers and optional source digest/label assertions. Labels are inert metadata. No fuzzy offsets, Git prelude, filesystem writes or external content.
Choose for: Validate and apply a model-generated unified patch to supplied document text Reject stale patch context before accepting a document revision
Outside this profile: Multi-file patches, Git binary patches, rename metadata, fuzz or CRLF text Filesystem access, path safety validation, or applying a patch to a repository
Extract top-level pipe tables from supplied Markdown into bounded cell arrays with exact source offsets, alignment and width findings. Uses an explicit line-based subset: table starts at document start or after a blank line, three-hyphen delimiters, fences excluded, inline markup preserved.
Choose for: Extract structured rows and cell provenance from Markdown reports Check pipe table widths without silently dropping or padding cells
Outside this profile: Full CommonMark or GFM parsing, nested containers, HTML tables or inline rendering Automatic schema inference, typed values or ambiguous one-hyphen delimiters
Audit supplied retrieval/document chunks against their exact source spans and compute verified coverage, uncovered ranges, overlap depth and policy findings. Invalid chunks never contribute coverage. Checks identity and coverage only, not retrieval quality or semantic relevance.
Choose for: Verify exported RAG chunks reconstruct and cover their source document Find stale chunk text, gaps or forbidden overlaps before indexing
Outside this profile: Semantic chunk quality, source authenticity, OCR correction or embedding validation Comparing independent ground-truth annotation datasets
Extract exact JSON object/array candidates from caller-supplied text using explicit json-fence or balanced-container mode. Selects only one unambiguous valid candidate, rejects duplicate decoded keys and nonfinite numbers, and never repairs invalid JSON or executes content.
Choose for: Recover a strict JSON object from a model response with source-span evidence Reject ambiguous structured outputs instead of choosing the first JSON block
Outside this profile: JSON repair, JSON5, primitive JSON roots, schema validation or interpreting prose Guaranteed distinction between literal braces in prose and intended JSON in balanced mode
Repair 1–5 supplied JSON-like texts under an explicit conservative grammar: comments, trailing commas, ASCII unquoted keys, single quotes, Python True/False/None, leading BOM and one enclosing JSON fence. Return unchanged originals, repaired text, parsed values, exact edit traces and independent item rejections. No missing values, delimiters or truncated data are inferred.
Choose for: Repair known syntactic defects in caller-supplied JSON-like text Preserve original text and inspect every change before trusting a structured artifact
Outside this profile: Arbitrary JSON5 or Python parsing, schema validation, semantic correction or guaranteed repair Completing truncated values, guessing missing delimiters or selecting duplicate keys Large documents, arbitrary-precision numbers or a cheapest single-call guarantee
Repair one JSON document, require a valid caller-schema result, serialize and SHA-256 hash it before one x402 settlement. Fixed four-step local profile; no partial result, RFC 8785 or guaranteed delivery.
Choose for: The caller needs all four successful local steps as one x402-only fixed job Withhold partial results and stop before new settlement if repair or schema acceptance fails
Outside this profile: Arbitrary workflows, operation lists, bindings, external requests, MPP, or per-step pricing Only repair, only validation, or a job that does not need an artifact digest Full JSON Schema, RFC 8785, semantic truth, authenticity or guaranteed delivery