Loading page
Developer toolsV2 Beta
Check a JSON document. See where it needs attention.
Try a fictional example or open your own file. The inspector checks the document’s structure and internal relationships, then shows the result beside your input.
Fictional example · Source-backed observation
A fictional field session linked to its station log. Position remains unknown.
Edits are not saved when you leave or reload. Save JSON to keep a local copy.
Choose Check document to see which checks pass and where to make changes.
A passing document can still contain incomplete or incorrect information. These checks do not establish source authenticity, sensor accuracy or a scientific conclusion.
This tool checks one supported JSON document at a time. It does not accept source media, ZIP archives, intake receipts, sensor profiles or provider-score documents. Use their package evaluators for those checks.
| Document kind | Document version |
|---|---|
observation | 0.1.0 |
observation_context | 0.1.0 |
research_entities | 0.1.0, 0.2.0, 0.3.0, 0.4.0 |
claim_history | 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0 |
Document versions identify the JSON contract; they are separate from the package version. Browser limits are 1 MiB, 64 nested levels and 20,000 values. For larger documents, run the package parser locally.