Service details

JSON Repair and Format Conversion

Repair supported JSON syntax or convert JSON/YAML with an explicit change log. Your assistant calls the service and brings the result back into your task.

Conservatively repair JSON syntax or convert JSON and safe YAML while recording every repair

0.005 USDC per accepted request

Paid only. No free trial for this operation.

Use this service →

This operation needs paid setup. New to Mekler? Start with a free sample task →

Know its boundaries.

Inventing missing keys or values, repairing truncated structures, semantic truth checks, schema validation or preserving YAML comments and formatting.

Data handling

Supplied inputs, source results and proofs are excluded from telemetry. Completed results remain encrypted for 30 day original-proof recovery. Feed URLs use robots/DNS controls; package names go only to PyPI/npm. TLS connects only to the public hostname on port 443. Document and schedule processing is local to the service runtime.

Input example and exact contract

{
  "text": "{\"service\":\"Mekler\",}",
  "input_format": "json",
  "output_format": "yaml",
  "request_id": "json-conversion-example-001"
}

API reference: input, output and error schemas →

Example output

{
  "status": "ok",
  "outcome": "converted",
  "input_format": "json",
  "output_format": "yaml",
  "output": "service: Mekler\n",
  "transformations": [
    {
      "operation": "remove_trailing_comma",
      "offset": 19
    }
  ],
  "reason": null,
  "observed_at": "2026-10-20T00:00:00Z",
  "limitations": [
    "Only BOM removal, complete JSON markdown fences and trailing commas outside quoted strings are repaired; offsets refer to each transformation stage.",
    "No missing values, keys, closing delimiters or quotes are guessed. Duplicate keys, nonfinite numbers and unsupported syntax produce abstention.",
    "Numeric values must round-trip through their serialized representation without decimal-value loss; unsupported precision produces abstention instead of rounding.",
    "YAML uses safe YAML 1.1 scalar interpretation; timestamps remain strings, aliases/anchors/explicit tags are rejected, and only JSON-compatible string-keyed values are supported.",
    "Formatting and comments are not preserved. A completed conversion or abstention diagnostic is charged; no semantic truth or schema validity claim."
  ]
}

Calling, result interpretation and recovery

Calling

Endpoint: POST /v1/data/json/repair-or-convert-document
Content type: application/json
Input: All fields, formats, defaults and limits are specified in requestBody. request_id must be 16–64 ASCII letters, digits, underscores or hyphens; use a fresh value per new purchase.

Interpret the result

Status: ok means the documented bounded operation completed; inspect explicit coverage and limitations.
Result: Response schema describes each output. Null means missing/unknown, never measured zero. outcome=abstained has null output and a reason; numeric_precision_unsupported preserves the supplied value by declining conversion.
Recovery: Use the original body and payment proof after timeout, pending settlement or quote expiry.

Limits

Request bytes

24000

Semantics

No work occurs on unsigned quotes. Normalize and bind the complete input before payment.
Successful results are encrypted for 30 day original-proof recovery.
Incomplete operation or source/storage failure is uncharged. A completed diagnostic or zero-match lookup is charged.
JSON and YAML numeric values that cannot round-trip without decimal-value loss return an explicit charged abstention diagnostic; no rounding is applied.

Payment and recovery

Price

0.005 native USDC per completed operation

Network

Solana mainnet or Base mainnet

Protocol

x402 v2 exact

Quote

POST the intended JSON unsigned for one input-bound 402; no work/source retrieval occurs. Sign one offer and resend identical JSON. Work and encrypted storage complete before settlement.

Authorization

Choose one accepts entry with a standard x402 v2 client. Check native USDC, network, recipient, amount and intended input before signing. Solana uses an SVM transaction; Base uses an EOA EIP-3009 authorization (USD Coin version 2). Send the proof with identical JSON input. No API key, token approval, bridge or Solana wallet is needed for Base. Never automatically fall back to another network.

Retry

Preserve identical JSON and original proof for 30 day result recovery; do not buy again after a timeout or pending result. Fresh request_id creates a new paid operation.

Finality

A 202 is pending. Finalized delivery carries PAYMENT-RESPONSE; provisional delivery is separately labeled and does not establish finality. Preserve the original proof instead of buying again.

Expiry

Ongoing service under recurring monthly authority. Budget warnings do not stop service. Short-lived quotes and recovery retention still expire.

Networks

solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
eip155:8453

Assets

Solana:5eykt4usfv8p8njdtrepy1vzqkqzkvdp: EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v
Eip155:8453: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Fees

CDP sponsors the payment transaction gas on both networks. The service price is the same on either network; wallet funding or exchange fees are separate.

Request binding

The server authenticates the complete quote and input and atomically binds the first accepted authorization to them. Standard Base EIP-3009 signs the money terms and nonce, not HTTP content. Keep signatures private; do not reuse an authorization for another quote, operation or body.