FlowMint JSON Repair

Repair one malformed JSON document per run using deterministic CPU processing. No LLM, proxy, URL fetching or external API is used.

Input

{"operation":"json-repair","payload":{"text":"{hello: \"world\",}"}}

Only json-repair is supported. payload.text contains a single document (object, array or scalar), not a batch. Serialized payload limit:128KiB; worker deadline:5 seconds. Unsupported or overly complex input fails. Repair restores syntax; ambiguous input can have multiple interpretations. Check the result before relying on its meaning.

Output

Canonical key-value record OUTPUT and one default-dataset record:

{"operation":"json-repair","result":{"text":"{\"hello\": \"world\"}","value":{"hello":"world"},"changed":true}}

result.text is valid JSON text; result.value is its parsed value. Customers can run through Apify Console or API without contacting the creator. Results remain in their run storage; avoid submitting secrets or data you cannot process on Apify.

Pricing

Prepared PPE configuration: one repair event at $0.003 plus automatic apify-actor-start at $0.00005. A successful one-document run costs $0.00305. Platform usage is included. Dataset output has no additional event charge. Actual activated pricing is shown by Apify; this candidate is not yet published.

Invalid input may still incur the platform start fee. Insufficient repair budget returns an error without successful output. Set maximum run charge to at least $0.00305. No additional repair is attempted when an event limit is reached.

Failures and repeated runs

Each new run is a new order. A completed same-run restart does not charge or append again. If a run stops during charging or output delivery, automatic recharge is disabled; use the run ID when reporting an issue. A charge can succeed before storage delivery fails; this requires billing reconciliation, not a blind retry. An available OUTPUT may be usable even if dataset delivery failed.

Report defects through the Actor Issues tab with run ID and a non-sensitive description. Never include API tokens, private credentials or confidential input. No bespoke integrations or uptime SLA are offered; platform support obligations still apply.