Json Repair
by ManyLives Tools in AI models & inference
Repair broken JSON (typical of model output) into valid JSON: removes code fences, comments and stray text, fixes single quotes, unquoted keys, trailing commas, Python literals (True/None) and truncated output. Optionally checks the result against a JSON Schema.
https://api.manylives.me/paid/json/repair- Price
- $0.002
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 416 ms
- 514 ms slowest 5%
- Last check
- Passed
- 4 h ago, next any minute now
Reliability
How to call it
POST https://api.manylives.me/paid/json/repair
Each call costs $0.002 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.manylives.me/paid/json/repair
content-type: application/json
{
"text": "```json\n{name: 'Ada', tags: ['a','b',],}\n```"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
schema | string | No | optional JSON Schema object to validate the repaired value |
text | string | Yes | the broken JSON as a string (required, max 500,000 characters) |
Example response
The provider's example. We can't check it without paying.
{
"fixes": [
"removed code fence",
"quoted keys",
"removed trailing commas"
],
"issues": [],
"json": {
"name": "Ada",
"tags": [
"a",
"b"
]
},
"repaired": true,
"schema_valid": true,
"valid": true
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.002.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.manylives.me/paid/json/repair' \
-H 'content-type: application/json' \
--data-raw '{"text":"```json\n{name: '\''Ada'\'', tags: ['\''a'\'','\''b'\'',],}\n```"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.manylives.me/paid/json/repair' \
-H 'content-type: application/json' \
--data-raw '{"text":"```json\n{name: '\''Ada'\'', tags: ['\''a'\'','\''b'\'',],}\n```"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.manylives.me%2Fpaid%2Fjson%2Frepair&method=POST
const res = await pay("https://api.manylives.me/paid/json/repair", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"text": "```json\n{name: 'Ada', tags: ['a','b',],}\n```"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.manylives.me/paid/json/repair",
json={
"text": "```json\n{name: 'Ada', tags: ['a','b',],}\n```",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 4 h ago | Passed | 402 | 456 ms | $0.002 |
| 8 h ago | Passed | 402 | 412 ms | $0.002 |
| 12 h ago | Passed | 402 | 418 ms | $0.002 |
| 16 h ago | Passed | 402 | 396 ms | $0.002 |
| 20 h ago | Passed | 402 | 519 ms | $0.002 |
Show 10 older checks
| 24 h ago | Passed | 402 | 416 ms | $0.002 |
| 28 h ago | Passed | 402 | 410 ms | $0.002 |
| 32 h ago | Passed | 402 | 405 ms | $0.002 |
| 36 h ago | Passed | 402 | 490 ms | $0.002 |
| 40 h ago | Passed | 402 | 441 ms | $0.002 |
| 43 h ago | Passed | 402 | 514 ms | $0.002 |
| 47 h ago | Passed | 402 | 571 ms | $0.002 |
| 2 days ago | Passed | 402 | 501 ms | $0.002 |
| 2 days ago | Passed | 402 | 505 ms | $0.002 |
| 2 days ago | Passed | 402 | 482 ms | $0.002 |