Our CLI makes it easier to work with locally-accessible files or web pages containing structured data. Similar to the playground, it provides subcommands for validation and syntax conversion, and can be used by humans, machines, or agents.
Installation
For each release, we provide precompiled binaries for different operating systems and architectures. Double check your system requirements, and then use one of the methods below before continuing to verify your installation.
Verify Installation
Once installed, execute the schemamarkup command and verify that it prints some basic information.
$ schemamarkup --versioncli name=schemamarkup version=1.202606.4
cli/build time=2026-06-25T01:42:47Z node=1b027e87-e11d-48db-8461-4a85a17bab4f
cli/runtime os=linux arch=amd64If you see an error message (or no output at all), check some of the common problems below.
Authentication
Authenticate using an Access Token to access higher usage limits of paid plans. The token may be set using one of the following methods, optionally including the Bearer prefix. Remember: tokens are sensitive and must be managed securely.
SCHEMAMARKUP_API_TOKEN=cln...environment variable with sensitive value.--api-token=cln...global flag with sensitive value.--api-token=@path/to/token.txtglobal flag with sensitive value read from file path.
If you use the --api-token global flag, be sure to include it before the sub-command name and flags.
schemamarkup --api-token 'cln...TOKEN...' [command] [command-flags]Commands
export— Tidy or convert a document to alternative RDF encodings.mcp— Run a local Model Context Protocol Server for agent-focused workflows.process— Process a document and return an annotated dataset and messages.validate— Validate a document and return validation messages with source offsets.
Global Flags
- string
- bool