Use case
Data engineers or analysts, when having coding agents such as Claude Code or Codex query an enterprise data warehouse, work with table and field relationships so the agent writes queries that match business meaning.
Hand-maintained data dictionaries and docs, or pasting schema into the prompt on each request.
Agents do not know what fields mean in business terms and write semantically wrong queries; the old way relies on hand-maintained data dictionaries or pasting schema into each prompt, which is repetitive and drifts.
xOcto's call
Demand is evidenced
The trend is that for agents to actually do work, what is missing is not the model but a semantic layer over business data. A wedge is ontology maintenance for verticals with many legacy tables such as retail or manufacturing, charged per data source or per project rather than shipped as a generic plugin.
Reason to use it
Why users would choose it
Inference: compared with pasting schema each time, it persists the ontology and evolves it with use, removing the step of re-explaining field meaning, so teams maintaining one warehouse long term would choose it when repeatedly having agents write queries.
Where the easy answer breaks down
The tension worth following
An English validation note will follow from the public evidence.
If this is your job
Worth trying. Inference: compared with pasting schema each time, it persists the ontology and evolves it with use, removing the step of re-explaining field meaning, so teams maintaining one warehouse long term would choose it when repeatedly having agents write queries.
Entry and what to borrow
The trend is that for agents to actually do work, what is missing is not the model but a semantic layer over business data. A wedge is ontology maintenance for verticals with many legacy tables such as retail or manufacturing, charged per data source or per project rather than shipped as a generic plugin.