realisRealis

The verifying integration compiler

The docs say one thing.
Realis returns the receipt.

Realis reads the docs, calls the real API, and signs every mismatch as proof anyone can replay.

Watch it run

One command. A real verification against a live API, from crawl to a signed finding.

realis ▸ verifylive
$ realis verify api.stripe.com/docs --sandbox sk_test_…
crawldocs · 42 pages · provenance stored
infer31 endpoints · OpenAPI 3.1 · conf 0.91
probeGET /v1/charges · 200 · 142ms
verifyamount — docs say number, API returned "4200" (string)
skeptics4 / 4 confirm · not a hallucination
emitfinding signed · ed25519:9f2a…41 · replayable
done · 1 finding · 0.6s

allowlisted sandbox hosts only · destructive endpoints never auto-probed

Five jobs, one verified pass

A docs URL and a sandbox key in. Verified code and signed evidence out. Every stage records what it saw.

01

Crawl

Render the vendor's docs with Playwright and snapshot every page, so each claim traces back to a source.

docs → snapshots
02

Infer

Segment, dedup, and normalize into a draft OpenAPI 3.1 spec with a calibrated confidence per endpoint.

snapshots → draft spec
03

Probe

Call the live API with your sandbox key. Allowlisted hosts only, recorded as replayable cassettes.

spec → cassettes
04

Verify

Diff docs against reality. N adversarial skeptics try to refute each finding; only survivors are recorded.

cassettes → findings
05

Emit

Generate typed SDKs, an MCP server, tests, and a signed report from what is actually true.

findings → artifacts

Every other tool trusts the docs

Generators need a spec you already have. Doc scrapers stop at a draft. Realis is the only one that calls the real API and keeps the receipts.

ToolDocs to specLive verificationFindings corpus
Stainless · Speakeasy · Fern
OpenAPI Generator
SpeCrawler · Doc2Spec
Realis

Not just a verifier

Four things a plain docs-checker cannot do. This is the moat.

Trustless attestation

Every finding ships a signed, sanitized bundle anyone can replay to confirm it, without your credentials.

bundle.json verified
ed25519:9f2a7c…41be · replay ok

Adversarial verification

N independent LLM skeptics try to refute each finding. Only the ones that survive get recorded. Hallucinations die here.

survived 4/5

Semantic diff to SemVer

A re-crawl diffs behavior, classifies the break, picks the SemVer bump, and a CI tripwire fails the consumer's build.

1.4.22.0.0BREAKINGCI ✗

Calibrated confidence

Per-endpoint scores are statistically calibrated with isotonic regression, so 80% confident means right 80% of the time.

Broken docs, in the open

Confirmed findings are sanitized, signed, and published to a public index anyone can search and replay.

0
findings signed
vendorclaim → realitysev
reqrespage: string numberLOW
restcountriescurrencies: array objectMED
openlibrarysubjects: required absentHIGH
pokeapiheight: cm decimetresLOW
spacexdate_utc: date epoch msMED
jsonplaceholderid: persisted always 101LOW

Stop shipping against docs you never checked

Point Realis at an API. Get back verified SDKs, an MCP server, and proof of every place the docs were wrong.

Start verifyingrealis verify <docs-url> --sandbox <key>