Playground
See how your data looks in ODIN. Select an example or paste your own.
JSON Input
ODIN Output
company = "Acme Corporation" region = "North America" active = ?true metadata = ~ {customers[] : id, name, active, balance, contact.email, .phone} ##12345, "Acme Corporation", ?true, #15750.42, "info@acme.com", "512-555-0100" ##12346, "Globex Industries", ?true, ##8320, "sales@globex.com", "415-555-0199" ##12347, "Initech LLC", ?false, ##0, "support@initech.io", "737-555-0142" ##12348, "Umbrella Corp", ?true, #42100.75, "accounts@umbrella.net", "310-555-0187" ##12349, "Wayne Enterprises", ?true, ##98500, "bruce@wayne.com", "212-555-0134"
Standard Reference
The complete ODIN notation spec: types, modifiers, paths and everything you need to read and write ODIN fluently.
Read the specSchema Reference
Define validation rules, constraints, and reusable types. Enforce structure across your entire data pipeline.
Define your typesTransform Reference
Map fields between formats with built-in verbs, conditionals and format-aware output. No code required.
Transform dataSchema Library
Browse 300+ production-ready schemas for insurance, healthcare, finance, legal and more. Ready to validate.
Browse schemas