{"slug": "pinecone-introduces-nexus-engine-for-compiling-business-context-into-structured", "title": "Pinecone Introduces Nexus Engine for Compiling Business Context into Structured Data for AI Agents", "summary": "Pinecone launched Nexus, a knowledge engine that compiles enterprise business context into structured data for AI agents, reducing token costs and improving accuracy. Early adopters in legal and financial sectors saw up to 15x lower token spend and 90% accuracy, outperforming traditional RAG systems. The product is now generally available with connectors for Box, Microsoft OneLake, and more.", "body_md": "Now generally available, [Pinecone Nexus is a \"knowledge engine\" for AI agents](https://www.pinecone.io/blog/pinecone-nexus-public-preview/) that transforms enterprise data into a structured layer agents can query directly. It enables teams to ingest and curate business context once for all, making it reusable across agents and reducing token costs while improving accuracy.\n\nPinecone argues that while large language models \"are great at world knowledge\" and vector databases make it easy to \"find specific information buried across files\", enterprises depend on a different layer of knowledge: business context. This context usually lives scattered through \"contracts, wikis, HR docs, meeting notes, support tickets, and financial records\".\n\nAgents can search through this information, but doing so every time they start a task is highly inefficient and leads to higher token costs as well as slower and potentially incomplete answers.\n\nPinecone Nexus is a knowledge engine that closes that gap. It compiles an enterprise's distributed knowledge into a structured layer agents can query directly, shifting token spend out of the per-query retrieval loop and into a one-time curation step.\n\nPinecone reports that early adopters of Nexus have seen significant performance gains, particularly in financial services and legal research. In the legal domain, Nexus completed all assigned tasks, compared to just 6% for a coding agent and 66% for a RAG system. The RAG system struggled with \"doctrine synthesis, cross-case reasoning, and coverage questions, the shapes that require many sources assembled into one answer\". Token spend was also substantially lower, reduced by approximately ~9–15×, according to Pinecone.\n\nSimilar improvements were found for enterprise data management, with a 90% accuracy, vs. 65% of a RAG system, and a curation cost of $0.0038 per document.\n\nPinecone Nexus is built around the concept of *workspace*, the top-level container for all resources, usually associated to a team or business unit. Within a workspace, data is organized into *contexts*, each representing a specific dataset or knowledge domain. A *manifest* defines how raw data sources should be ingested and converted into structured knowledge. Through manifests, subject matter expertise is incorporated directly into the system:\n\nA subject matter expert can design a blueprint defining the artifact types and relationships that encode their domain knowledge into the curation layer before any query runs. The agent isn't left to figure out the structure of the corpus at query time. It inherits the SME's understanding of it.\n\nData ingestion is handled through connectors that support a range of sources, including local files, Box, and Microsoft OneLake. Support for Google Drive, Slack, GitHub, Notion, Confluence, and S3 is expected soon, according to Pinecone. Once ingested and curated, the data can be queried via KnowQL, which is used by agents, chatbots, and recommendation systems alike.\n\nPinecone Nexus includes a preview playground where users can connect their data sources, design a context, and run a query to validate their approach. It also offers a BYOC (Bring your own Cloud) deployment options for environments where \"data residency, security, and compliance are non-negotiable\".\n\nOther existing solutions similar to Pinecon Nexus include [Cognite](https://www.cognite.com/), [RationalAI](https://www.relational.ai), [LlamaIndex](https://developers.llamaindex.ai/python/framework/) and others.", "url": "https://wpnews.pro/news/pinecone-introduces-nexus-engine-for-compiling-business-context-into-structured", "canonical_source": "https://www.infoq.com/news/2026/07/pinecon-nexus-knowledge-engine/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global", "published_at": "2026-07-18 14:00:00+00:00", "updated_at": "2026-07-18 14:29:39.528863+00:00", "lang": "en", "topics": ["ai-products", "ai-infrastructure", "ai-agents", "ai-tools", "large-language-models"], "entities": ["Pinecone", "Pinecone Nexus", "Cognite", "RationalAI", "LlamaIndex", "Box", "Microsoft OneLake"], "alternates": {"html": "https://wpnews.pro/news/pinecone-introduces-nexus-engine-for-compiling-business-context-into-structured", "markdown": "https://wpnews.pro/news/pinecone-introduces-nexus-engine-for-compiling-business-context-into-structured.md", "text": "https://wpnews.pro/news/pinecone-introduces-nexus-engine-for-compiling-business-context-into-structured.txt", "jsonld": "https://wpnews.pro/news/pinecone-introduces-nexus-engine-for-compiling-business-context-into-structured.jsonld"}}