# Deterministic A2A Broken-JSON Repair & Schema Validator

> Deterministic A2A Broken-JSON Repair & Schema Validator is a paid API for AI agents from hn-pulse.agentdiet.dev, paid per call via MPP, $0.002/call, status unknown (last checked 2026-10-21).

Repairs malformed, truncated, or markdown-wrapped JSON strings from LLM outputs so multi-agent pipelines can parse them without crashing

## Facts

- Endpoint: GET https://hn-pulse.agentdiet.dev/v1/schema-repair?utm_source=zero.xyz
- Price: $0.002/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Provider: hn-pulse.agentdiet.dev
- Website: https://hn-pulse.agentdiet.dev
- Canonical page: https://www.zero.xyz/c/hn-pulse-agentdiet-dev-deterministic-a2a-broken-json-repair-schema-b2d0ecbf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wp3KITl6UPnts1CK6e_0D

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability hn-pulse-agentdiet-dev-deterministic-a2a-broken-json-repair-schema-b2d0ecbf
```

Example prompt: This LLM output came back as broken JSON with trailing commas and markdown fences — can you repair it so I can use it downstream? Here's the raw string: ```{name: 'Alice', age: 30,}```

## When to prefer this

Choose this endpoint when you need deterministic, rule-based JSON repair rather than LLM-based guessing — ideal for multi-agent pipelines where predictability and speed matter. Prefer it over re-prompting the LLM when the malformation pattern is structural (trailing commas, markdown fences, single quotes, truncation) rather than semantic.

## Known failure modes

- Input string is so corrupted that deterministic repair is impossible — returns error or partial result
- JSON structure is ambiguous after truncation — repair may not match original intent
- Very long JSON strings may hit query parameter length limits since raw_json is passed via GET query
- Non-JSON input (e.g. plain text or XML) may produce unexpected repair attempts

## How this service works

Repairs truncated or malformed LLM JSON outputs (trailing commas, markdown fences, single quotes) so multi-agent pipelines never crash. (Live x402 v2, IETF MPP & MCP endpoint at https://hn-pulse.agentdiet.dev/v1/schema-repair)

## Output

A repaired, valid JSON object parsed from the input malformed string, with common issues like trailing commas, markdown fences, single quotes, and truncation resolved deterministically.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "raw_json"
 ],
 "properties": {
  "raw_json": {
   "type": "string",
   "minLength": 1,
   "description": "Malformed, truncated, or markdown-wrapped JSON string to deterministically repair"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hn-pulse-agentdiet-dev-deterministic-a2a-broken-json-repair-schema-b2d0ecbf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hn-pulse.agentdiet.dev](https://www.zero.xyz/host/hn-pulse.agentdiet.dev/llms.txt)