Schemas
The JSON Schema and OpenAPI documents Monomer publishes, and what each one describes. An input that matches its schema has the right shape; Monomer still checks names, references, and your role when it saves or runs it.
| Document | Describes |
|---|---|
| Agent OpenAPI | Every Agent API operation: discovery, Organization and Workspace operations, the MCP endpoint, and OAuth |
| Agent schema | Requests and responses of the resource operations: list, read, search, create, edit, and invoke, with each resource path and action |
| Problem Details schema | The body of every agent API error; see Errors |
| Connector schema | Warehouse connection settings and sign-in methods for each warehouse type |
| Semantic model schema | A semantic model: source tables, entities, dimensions, and measures |
| Metric display schema | Number, currency, and percentage formats, decimal places, supported units, and ISO 4217 currency codes |
| Metric schema | A metric built from measures or other metrics |
| Query schema | A metric question: metrics, group-bys, time range, filters, order, and row limit |
| Time spine schema | The table with one row per period that a connector uses for cumulative, conversion, and offset metrics; see Set up a Calendar table |
| Dashboard schema | A dashboard definition: inputs, queries, widgets, layout, and schedules |
Schemas reference one another by their $id. The agent schema reuses the connector, semantic, and dashboard schemas for the definitions inside a resource, so an agent can follow references from any operation to the exact definition shape. Task guides show complete examples: Add a warehouse connection, Define a metric, and Create a dashboard.