# Strale LLM Output Validator

> Strale LLM Output Validator is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054/call, status unknown (last checked 2026-09-14).

Validates LLM-generated output against an expected schema, returning a structured audit record with cryptographic chain hashing.

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/llm-output-validate
- Price: $0.054/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-llm-output-validator-8f03c05d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QSXDYYcyJMB6ABiXRHxAv

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 strale-llm-output-validator-8f03c05d
```

Example prompt: Can you validate this LLM output against my expected schema — the schema is '{"type":"object","properties":{"name":{"type":"string"},"score":{"type":"number"}}}' — and give me the audit record with the cryptographic hash?

## When to prefer this

Choose this endpoint when you need not just schema validation but also a cryptographically verifiable audit trail of the validation event — particularly in regulated, compliance-heavy, or multi-agent pipeline contexts where tamper-evident records of AI output quality are required. Prefer this over generic JSON validators when you need the trust layer (chain hashing, audit records) that Strale provides, or when operating in environments requiring AI governance documentation.

## Known failure modes

- Invalid or malformed expected_schema input returns a parse error
- LLM output not provided or empty may result in a validation error
- Schema mismatch returns detailed non-conformance details
- Network timeout or service unavailability returns a 503 error
- Malformed JSON in expected_schema returns a 400 bad request

## How this service works

The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.

## Output

Returns a structured validation result indicating whether the LLM output conforms to the expected schema, along with a detailed audit record that includes a cryptographic chain hash for tamper-evident traceability.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "expected_schema": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-llm-output-validator-8f03c05d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)