StackMap
Subscribe
Explore / auto-ontology
NVIDIA

auto-ontology

NVIDIA's ontology framework for agentic analytics: generate ontologies from metadata, ground agents in governed business meaning, validate generated SQL, and serve context via MCP, CLI and API.

13,938 1,222 Python Apache-2.0updated today
View on GitHubDispute this mapping →
Curator's take

Reach for it when agents answer business questions across many sources with conflicting definitions — the ontology pins metric meaning, validates queries and returns the SQL with every answer, and certified corrections flow back in. Its own README says it: one clean source and a fixed question set don't need this; direct SQL or a semantic layer is enough.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside auto-ontology. Ranked by curator confidence.

pairs wellalternativealternativealternativeslayercontext-ontology-acceleratorneocartaEvoOntologyauto-ontology
pairs wellalternativebuilt withpick a node for the why · open it from the panel
Weekly digest
README.md2 min read

Auto Ontology

#1 on the BEAVER leaderboard #2 on the BIRD-Interact leaderboard

Agents can retrieve documents and query databases, but reliability gates agentic analytics: a revenue metric answered faster is worth nothing if the number is wrong. Agents need context to answer accurately: what each business concept means, where it lives, how it connects, how to calculate it, where it comes from, and whether to trust it. An ontology holds that context: a shared, governed map from the concepts people ask about to the data behind them. NVIDIA Auto Ontology is an open library that builds that ontology automatically from enterprise metadata, reconciles definitions across systems, and exposes it to any agent harness through MCP, CLI, and API. It complements the semantic models customers already own, and Apache Ossie keeps it portable.

It enables developers to:

  • Discover: generate enterprise ontologies from metadata; connect existing ontologies and semantic models; build AI-ready knowledge graphs.
  • Ground: give agents trusted business meaning for metrics, entities, and relationships; reconcile inconsistent definitions across systems.
  • Validate: test a draft with real questions before experts certify it; check generated queries against the catalog and the definitions retrieval surfaced; return the SQL and steps with every answer.
  • Expose: serve context to any agent harness through MCP, CLI, and API.
  • Learn: fold certified corrections and usage back into the ontology, so shared context improves with use.

An ontology matters most when:

  • questions are varied, open-ended, and ambiguous;
  • data spans many disparate sources with overlapping or conflicting definitions;
  • meanings must be reused and governed across runs, teams, and agents;
  • the model or its context budget can't hold the full documentation;
  • users ask in business terms and need routing to the right source and grain.

With one well-modeled source and a fixed set of questions, direct SQL may be enough.

Quickstart

This runs Auto Ontology with Docker Compose against Wide World Importers, Microsoft's sample sales database. You need Docker with Compose v2, uv, and an NVIDIA API key (nvapi-...) from build.nvidia.com.

  1. Clone the repository and create .env:

    git clone https://github.com/NVIDIA/auto-ontology.git && cd auto-ontology
    cp .env.example .env
    

    Then set these values in .env:

    DEFAULT_MODELS_API_KEY=nvapi-...
    AUTH_SECRET=<a long random string, e.g. from openssl rand -base64 32>
    APP_URL=http://localhost:3000
    POSTGRES_PASSWORD=<a new password>
    CONNECTION_STRINGS=postgresql://postgres:<the same password>@postgres:5432/wideworldimporters
    AUTO_ONTOLOGY_ADMIN_PASSWORD=<a new password>
    PGADMIN_PASSWORD=<a new password>
    

    Compose publishes Postgres, pgAdmin, and the web app on the host, so replace each default password before you start it. .env.example also sets an API key per model role: replace each nvapi-your-api-key-here with your key, or delete those lines so they fall back to DEFAULT_MODELS_API_KEY.

  2. Start Postgres and load the sample database. The seed script lives in auto-ontology-eval; pass it the Postgres password you set:

    docker compose up -d --wait postgres
    git clone https://github.com/NVIDIA/auto-ontology-eval.git ../auto-ontology-eval
    (cd ../auto-ontology-eval && uv sync && cp .env.example .env && \
      POSTGRES_PASSWORD='<the same password>' \
      uv run python scripts/se