Orionbelt Semantic Layer

Get a published JSON Schema by name. Returns the raw JSON Schema document as a JSON string so callers can validate documents locally without round-tripping them to the API.

Describe the contents of the model. Shows data objects (with columns and joins), dimensions, measures, and metrics. In multi-model mode, use this after loading a model to explore its structure.

Generate a Mermaid ER diagram for the model. Returns a Mermaid diagram script that visualises the data objects, columns, and join relationships in the model.

Return the join graph as an adjacency list. Shows the data object nodes and join edges (with cardinality and join columns) in the model. Useful for understanding table relationships.

Resolve which artefacts can still be added to a query (ACR). Artefacts Composability Resolution: given an anchor — your in-progress query, or one or more named artefacts — returns the dimensions, measures, and metrics that remain composable with it and are guaranteed to compile into a valid, fanout-free result. It walks the same join graph the compiler uses, so anything it reports is safe to add. Supply the anchor exactly one of two ways: - ``query_json`` — an in-progress QueryObject as a JSON string (recommended). Its ``select`` dimensions and measures form the anchor. - ``anchors`` — one or more artefact names. Repeated names are intersected. Omit both for a fresh query, where everything composes. Directly composable artefacts share a fanout-safe root with the anchor. CFL measures/metrics come from an independent fact and compose only through the Composite Fact Layer (UNION ALL at the shared grain); they are reported separately.

Get the OBSL-Core RDF graph for the model as Turtle. Returns the semantic model's RDF graph serialized in Turtle format. The graph follows the OBSL-Core ontology and can be used for semantic web integration or further analysis.

Execute a read-only SPARQL query against the model's RDF graph. Supports SELECT and ASK queries only (no INSERT/DELETE/UPDATE). The graph uses the OBSL-Core ontology.

Look up model artefacts (dimensions, measures, metrics). Two modes, selected by whether you pass ``query``: - ``query`` set → fuzzy, ranked search. Matches names and synonyms (exact, synonym, and fuzzy/partial) and returns ranked candidates — for "I don't know the exact name". ``name`` is ignored in this mode. - ``query`` omitted → exact, deterministic, complete enumeration (the authoritative set). No args → every dimension, measure, and metric; ``kind`` only → the complete set of that one kind; ``name`` → that exact artefact (optionally constrained to ``kind``). ``kind`` narrows either mode to one artefact kind.

Explain the lineage of a dimension, measure, or metric. Traces the composition chain from the named artefact down to the underlying data objects and columns. Useful for understanding how a measure is computed or where a dimension originates.

List canonical example queries authored alongside the model. Returns each example's name, description, and intent tags. Use ``get_example`` for full detail (query payload + compiled SQL preview).

Get a single example by name with its query and compiled SQL preview.

Compile and execute a semantic query (QueryObject), returning SQL + results. Pass ``query_json`` — a QueryObject as a JSON string. If no ``limit`` is set, a server-side default row limit applies.

Get the pre-loaded OBML YAML model source. Returns the original OBML YAML that was loaded into the API at startup. Useful for understanding the model definition in the author's terms. (Single-model mode only.)