# BoundaryGuard Full Safety & Validation Pass

> BoundaryGuard Full Safety & Validation Pass 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).

Runs a comprehensive pipeline of risk scanning, JSON extraction, schema normalization, and deterministic receipt generation in a single call before an agent proceeds

## Facts

- Endpoint: POST https://boundary-guard-x402.onrender.com/guard
- 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-bafcb4cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QK-0eRxg8oFo0RXWI_D0O

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-bafcb4cd -d '<json body>'
```

Example prompt: Before passing this LLM output to the next step, run the full boundary guard pipeline on it — risk scan for prompt injection and PII, extract and repair the JSON, normalize it against my declared schema, and give me a deterministic receipt I can log.

## When to prefer this

Choose this endpoint when you need all four safety/validation passes (risk scan + JSON extraction + schema normalization + receipt) run atomically in a single API call rather than chaining four separate endpoints. Ideal for agent pipelines where latency budget allows one round trip and you need a tamper-evident receipt for audit. Prefer individual sibling endpoints if you only need one specific pass.

## Known failure modes

- Input text too large or malformed — returns 400 with parsing error
- Schema normalization fails if target schema is not provided or is invalid
- Risk scan may flag false positives on benign content with credential-like patterns
- Service cold-start on Render.com free tier may add latency (503 or timeout)
- Payment not accepted or x402 protocol error — returns 402 with payment details

## Output

Returns a bundled result containing: risk scan findings (prompt injection, secrets, PII flags), the extracted/repaired JSON payload, the schema-normalized data object, and a deterministic receipt for audit or chaining. All four passes are applied in sequence before the agent is permitted to continue.

## Example request

```json
{
 "text": "The API response contains user data: {\"user_id\": 12345, \"name\": \"John Doe\", \"status\": \"active\"}",
 "policy": {
  "require_json": true,
  "max_risk_score": 39,
  "policy_version": "guard-v1",
  "block_issue_kinds": [
   "injection"
  ],
  "on_extract_failure": "retry",
  "on_normalize_failure": "retry"
 },
 "schema": {
  "type": "object",
  "properties": {
   "name": {
    "type": "string"
   },
   "status": {
    "type": "string"
   },
   "user_id": {
    "type": "integer"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/boundary-guard-x402-onrender-com-bafcb4cd/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)