# BoundaryGuard Schema Normalize

> BoundaryGuard Schema Normalize 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).

Normalizes untrusted or loosely-typed data against a declared JSON Schema before it is persisted, chained, or executed by an agent.

## Facts

- Endpoint: POST https://boundary-guard-x402.onrender.com/schema-normalize
- 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-64a4966d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_88MWj9ZIMdrZ0hzUzGozl

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

Example prompt: Before you save this user-submitted payload to the database, normalize it against our declared JSON Schema — coerce types, fill in defaults, and reject anything that can't be made to conform.

## When to prefer this

Choose this endpoint when you need to enforce strict schema conformance on data that originated from an untrusted source, a language model, or user input before it is written to a database, passed to a downstream API, or used in an agentic chain. It is especially valuable in multi-step agent pipelines where one model's output feeds the next step's input and type safety is critical.

## Known failure modes

- Payload cannot be coerced to declared schema — returns validation error with field-level details
- Schema is invalid or unparseable — returns schema parse error
- Input data is completely unparseable — returns extraction failure
- Missing required fields with no default — returns missing field error
- Service unavailable on cold start (Render free tier) — returns 503 or timeout

## Output

Returns a schema-normalized JSON object where all fields have been coerced to their declared types, required fields are validated, defaults applied, and non-conforming values flagged or rejected, along with a normalization receipt.

## Example request

```json
{
 "data": {
  "age": "30",
  "name": "John"
 },
 "text": "Sample user input for normalization and risk assessment",
 "policy": {
  "require_json": false,
  "max_risk_score": 39,
  "policy_version": "guard-v1",
  "block_issue_kinds": [],
  "on_extract_failure": "retry",
  "on_normalize_failure": "retry"
 },
 "schema": {
  "type": "object",
  "required": [
   "name"
  ],
  "properties": {
   "age": {
    "type": "integer"
   },
   "name": {
    "type": "string"
   }
  }
 }
}
```

## More

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