{
  "schema_version": "1.1",
  "id": "s9:https://github.com/NVIDIA/auto-ontology",
  "slug": "auto-ontology-162lzu8",
  "url": "https://feed7.dev/p/auto-ontology-162lzu8",
  "title": "NVIDIA/auto-ontology",
  "why_included": "NVIDIA Auto Ontology gives data agents a metadata-derived semantic layer, with certified definitions, query validation, and provenance. Its MCP, CLI, and API interfaces expose that context to agent harnesses.",
  "summary": "Auto Ontology builds a graph-based layer from enterprise metadata, connecting business terms, columns, SQL attributes, and table relationships. People review and certify the generated definitions; agents can then produce SQL with validation steps and provenance. Context is exposed through **MCP, CLI, and API**.",
  "practical_implication": "For a builder connecting agents to structured data, the design separates discovery from trusted use: generate candidate definitions, certify them against real questions, then let the agent query from that catalog. The system can report when the ontology does not cover a question rather than inventing a supported answer.",
  "agent_context": "Auto Ontology builds a graph-based layer from enterprise metadata, connecting business terms, columns, SQL attributes, and table relationships. People review and certify the generated definitions; agents can then produce SQL with validation steps and provenance. Context is exposed through **MCP, CLI, and API**.\n\nFor a builder connecting agents to structured data, the design separates discovery from trusted use: generate candidate definitions, certify them against real questions, then let the agent query from that catalog. The system can report when the ontology does not cover a question rather than inventing a supported answer.\n\nThis is an open-source project described in its repository, not evidence of benchmark performance. Its setup depends on configured model endpoints, and deployment guidance warns that internal service ports must stay private because some endpoints lack their own authentication.",
  "source": {
    "name": "GitHub",
    "url": "https://github.com/NVIDIA/auto-ontology",
    "published_at": null
  },
  "source_class": "tool",
  "content_type": "GitHub Repo",
  "layer": "context",
  "domains": [
    "data"
  ],
  "topics": [
    "mcp",
    "retrieval",
    "agent-reliability"
  ],
  "verification": {
    "status": "needs_review",
    "label": "Needs Review",
    "method": "unverified",
    "verified_at": null
  },
  "uncertainty": [
    "This is an open-source project described in its repository, not evidence of benchmark performance. Its setup depends on configured model endpoints, and deployment guidance warns that internal service ports must stay private because some endpoints lack their own authentication."
  ],
  "connected_context": {
    "meaning": "Auto Ontology describes a reviewed path from enterprise metadata to agent SQL: generate business-term and schema relationships, certify definitions against real questions, then expose them with validation and provenance through MCP, CLI, or API. The repository description supports an architectural pattern, not measured performance, and flags private-port exposure as a deployment concern.",
    "corpus_size": 1009,
    "generated_at": "2026-11-05T11:04:10.384Z",
    "connections": [
      {
        "title": "AI on Your Lakehouse: Context Comes in Shapes, Not Queries — Zach Blumenfeld, Neo4j",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=kRkcNOsRyYg",
        "feed7_url": "https://feed7.dev/p/ai-on-your-lakehouse-context-comes-in-shapes-not-queries-zach-blumenfeld-0r4s9u5",
        "reason": "The graph-context candidate argues that relationships can expose information missed by vector search or Text-to-SQL; Auto Ontology gives that idea a concrete enterprise-data form by linking business terms, columns, SQL attributes, and tables, with certification before agent use."
      },
      {
        "title": "infiniflow/ragflow",
        "source_name": "GitHub",
        "source_url": "https://github.com/infiniflow/ragflow",
        "feed7_url": "https://feed7.dev/p/ragflow-0b0v2o1",
        "reason": "Both provide an inspectable context layer with agent access and traceability, but Auto Ontology centers on certified structured metadata for SQL while RAGFlow packages retrieval across mixed private data sources."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": null,
  "modified_at": null,
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/auto-ontology-162lzu8",
    "json": "https://feed7.dev/p/auto-ontology-162lzu8.json",
    "markdown": "https://feed7.dev/p/auto-ontology-162lzu8.md"
  }
}