aifinhub

Playground

Structured Schema Validator for Finance

Structured schema validator finance — paste LLM JSON, see missing fields, type mismatches, enum errors, and plausibility flags. Client-side.

Inputs
Paste + configure
Runtime
1–15 s
Privacy
Client-side · no upload
API key
Not required
Methodology
Open →

1 · Pick a schema

LLM research note on an investable idea. Must declare a probability, a thesis, and explicit invalidation conditions — every research output that cannot be falsified is just narrative.

Schema definition

FieldType / boundsReq
probabilitynumber [0 … 1]
Subjective probability the thesis plays out. 0..1 inclusive.
required
thesisstring ≥50 chars
Plain-English thesis. Minimum 50 chars — forces substance over one-liners.
required
convictionenum (low|medium|high)
Qualitative conviction bucket.
required
invalidation_conditionsarray ≥1 items
Explicit events that would kill the thesis. ≥1 item.
required
source_citationsarray ≥1 items
URLs or document IDs backing the claims. ≥1 item.
required

Valid example

{
  "probability": 0.62,
  "thesis": "Issuer SYNTHETIC_A's cloud-revenue mix is re-rating vs peers after three consecutive quarters of operating-margin expansion, while the sell-side model still assumes the legacy mix.",
  "conviction": "medium",
  "invalidation_conditions": [
    "Next quarter cloud-revenue growth prints below 20% YoY",
    "Operating margin contracts by more than 150 bps"
  ],
  "source_citations": [
    "10-Q FY2026 Q1, p.14",
    "Earnings call transcript 2026-02-11"
  ]
}

2 · Paste your LLM JSON

Validation runs in your browser as you type. Nothing is uploaded.

3 · Validation results

pass
5 / 5 fields ok
FieldMessage
probabilityok
thesisok
convictionok
invalidation_conditionsok
source_citationsok

What gets checked

  • Field presence, JSON type, enum values, numeric bounds, minimum string / array sizes.
  • Cross-field sanity (long stops below take-profit, leverage above retail limits, duplicate peer tickers).
  • Soft plausibility bands drawn from real-world issuer filings — out-of-band values warn, not fail.
  • Missing unit / GAAP-basis heuristics for revenue / EPS / EBITDA field names.

See methodology for why each schema is shaped the way it is.

Complementary tools

Planning estimates only — not financial, tax, or investment advice.