# BoundaryGuard JSON Extractor

> BoundaryGuard JSON Extractor is a paid API for AI agents from boundary-guard-x402.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Extracts or repairs a valid JSON payload from mixed prose, markdown, or malformed LLM output so downstream systems can parse it safely.

## Facts

- Endpoint: POST https://boundary-guard-x402.onrender.com/json-extract
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/boundary-guard-x402-onrender-com-c2e90ee5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_T8uwOw-H4iku6-3dUBSc4

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 boundary-guard-x402-onrender-com-c2e90ee5 -d '<json body>'
```

Example prompt: The model returned something like 'Sure! Here is the JSON you asked for: ```json {"name": "Alice", "age": 30,} ``` Hope that helps!' — can you extract just the clean, valid JSON object from that string?

## When to prefer this

Choose this endpoint when an LLM or agent pipeline produces output that wraps JSON in markdown, prose, or contains minor syntax errors like trailing commas or missing brackets, and you need a reliable, paid-per-call extraction step before passing data downstream. Particularly useful in agentic chains where structured data integrity is critical.

## Known failure modes

- No JSON-like structure found in input — returns error indicating nothing extractable
- Input is so malformed that repair is ambiguous — may return partial result or error
- Rate limit or payment failure via x402 — returns 402 or 429 status
- Service cold-start latency on Render free tier — first request may time out

## Output

Returns a clean, valid JSON payload extracted or repaired from the input text, ready for downstream parsing and use without any surrounding prose, markdown, or syntax errors.

## Example request

```json
{
 "text": "The user asked me to extract data. Here's the response: ```json\n{\"name\": \"Test User\", \"email\": \"test@example.com\", \"status\": \"active\"}\n``` Please parse this carefully."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boundary-guard-x402-onrender-com-c2e90ee5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from boundary-guard-x402.onrender.com](https://www.zero.xyz/host/boundary-guard-x402.onrender.com/llms.txt)