openOM docs
Machine-readable, broker-asserted data embedded in CRE offering memoranda - extracted once at the source, consumed cheaply everywhere. Pick your on-ramp:
๐ค Building an AI agent for CRE? Start here
Ground your agent in verified facts, not guesses - a deterministic read of a broker-asserted, hash-verified opinion instead of a hallucination-prone re-parse of the PDF. Grounding AI agents in openOM โ
Broker / author
You have OM PDFs and want them to carry structured, verifiable data.
Portal / consumer
You want to read and trust openOM data on PDFs you receive or host.
Implementer / developer
You are building against the standard in your own language or pipeline.
Learn
- What is an offering memorandum? - the definition, what an OM contains, and why its data is an assertion.
Reference
- Payload field reference - generated from the JSON Schema.
- Validation code catalog - every error/warning/info code the validator emits.
- Verify a PDF - drop a PDF and check its openOM state, entirely in your browser.
- Raw JSON Schema ยท JSON-LD context
An OM is an advertisement - a broker's opinion of value, agreed to by the seller before publication. openOM records who asserted it, unaltered, and as of when; it never claims the opinion is true. Verified means provenance, not truth. The engine is deterministic and inference-free; every payload is an identified party's opinion as of a date - assertions, never facts.