The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Agent JSON Reliability listing page.
Deterministic JSON repair + JSON Schema validation for AI agents.
No LLM. Safe refusal on ambiguity.
STATUS=BETA 0.1.0 · GitHub · PyPI · Official MCP Registry
Problem: agents emit malformed JSON (fences, trailing commas, single quotes). This tool inspects, safely repairs, and schema-validates that text. No LLM. No invented values.
| Path | Cost |
|---|---|
Local MCP (uvx agent-json-reliability) | Free |
Hosted POST /v1/json/inspect, /validate, /repair, /mcp | Free |
Hosted POST /v1/json/reliable | 0.003 USDC on Base via x402 |
Machine catalog: https://agent-json-reliability.onrender.com/v1/catalog
Skill: https://agent-json-reliability.onrender.com/skill.md
MCP client config (stdio, published package):
AI agents and software frequently emit malformed JSON: markdown fences, trailing commas, single quotes, True/False/None, and extra prose around one object.
Agent JSON Reliability is a deterministic pipeline for that failure mode:
valid_original, repaired, valid_final, schema_valid, unsafe_or_ambiguous, changes, errorsThis is not a generic jsonschema wrapper. Missing semantic values are never invented. Ambiguous input is refused.
Primary HTTP endpoint (local/self-hosted): POST /v1/json/reliable
MCP tools (same core functions): reliable_json, validate_json, repair_json, inspect_json
Malformed agent output:
Expected result (semantically equivalent valid JSON):
valid_original=falserepaired=truevalid_final=trueunsafe_or_ambiguous=falsejson → {"name":"alice","age":30}If a schema is supplied and satisfied: schema_valid=true.
Truncated input such as {"user": is JSON-intended but not deterministically repairable without inventing keys or values.
Expected:
200 (documented safe response)valid_final=falseunsafe_or_ambiguous=true or repaired=falseDo not treat a correct refusal as a product failure.
Binds 127.0.0.1:8770 by default. Set PUBLIC_BASE_URL to an HTTPS origin only when you expose the process yourself. Do not commit a temporary tunnel hostname as the canonical URL.
Public origin: https://agent-json-reliability.onrender.com
Inspect / validate / repair / MCP stay free. POST /v1/json/reliable returns HTTP 402 until an x402 PAYMENT-SIGNATURE settles 3000 atomic USDC (0.003) on Base (eip155:8453) via PayAI.
See examples/curl.md, examples/python.py, examples/javascript.js.
Remote examples use https://agent-json-reliability.onrender.com. Local default is http://127.0.0.1:8770.
Share URLs (optional, unverified telemetry tags):
/?source=github/?source=mcp-registry/?source=api-directoryPackage transport does not depend on a temporary public URL. Prefer uvx (above). From a checkout:
Remote HTTP MCP (POST /mcp) is for a running instance.
GET /.well-known/agent-services.jsonGET /.well-known/agent.jsonGET /.well-known/x402GET /openapi.jsonGET /llms.txt · GET /llms-full.txt · GET /AGENTS.md · GET /sitemap.xml · GET /robots.txtPOST /mcp JSON-RPC (tools/list, tools/call)No Hunter market database, no private reports, no Windows user paths, no collectors, no wallets in this package. Hosted /v1/json/reliable is x402-paid; local MCP and inspect/validate/repair are free.