{
  "schema": "hangingcontext.desk/1",
  "type": "story",
  "id": "1670",
  "slug": "databases-rebuild-for-agent-clients",
  "edition": "2026-11-17T12",
  "url": "https://hangingcontext.com/stories/2026-11-17/databases-rebuild-for-agent-clients/",
  "newsroom": "artificial-intelligence",
  "beat": "developers",
  "newsroom_title": "Artificial Intelligence",
  "angle": "The database vendors all shipped agent-ready features at once: agents are becoming the database's newest client.",
  "headline": "Your database's newest client is an agent, and the vendors just rebuilt for it",
  "dek": "Cockroach, Neo4j, Vespa, and Starburst all shipped agent-facing features. The common thread: agents ask worse questions than people, and the data layer has to absorb that.",
  "published_at": "2026-11-17T12:46:54Z",
  "labels": {
    "trust": "confirmed",
    "trust_text": "Confirmed · 4 Manifests",
    "newsroom": "Artificial Intelligence"
  },
  "source_count": 4,
  "publishers": [
    "cockroach-labs-blog",
    "neo4j-blog-rss",
    "starburst-data-blog",
    "vespa-blog"
  ],
  "sources": [
    "cockroach-labs-blog",
    "neo4j-blog-rss",
    "starburst-data-blog",
    "vespa-blog"
  ],
  "distinct_source_count": 4,
  "key_facts": [
    {
      "text": "Vespa says its full schema skill raised agent success on data-dependent tasks to 93%, from 9% without explanations, while cutting agent query volume by 75%.",
      "cites": [
        {
          "claim_ids": [
            "1794853137036435033",
            "1794853137020435032",
            "1794853137042435034"
          ],
          "manifest_id": "1794852817456426067"
        }
      ],
      "self_reported": true
    },
    {
      "text": "Starburst cites a VentureBeat survey finding 78% of respondents with agents on company data traced errors to missing or conflicting definitions.",
      "cites": [
        {
          "claim_ids": [
            "1794868916403575785"
          ],
          "manifest_id": "1794868386437573506"
        }
      ],
      "self_reported": true
    },
    {
      "text": "Neo4j's Virtual Graph is now generally available on Neo4j Aura on GCP, allowing zero-ETL knowledge graphs and GraphRAG systems.",
      "cites": [
        {
          "claim_ids": [
            "1794871066493591448",
            "1794871066495591449",
            "1794871066496591450"
          ],
          "manifest_id": "1794870585933589141"
        }
      ],
      "self_reported": true
    },
    {
      "text": "Cockroach Labs made bring-your-own-cloud available on Continuum, with clusters running in the customer's own cloud account at $1,000 per vCPU per year.",
      "cites": [
        {
          "claim_ids": [
            "1794850539398395234",
            "1794850539402395236",
            "1794850539405395238"
          ],
          "manifest_id": "1794850328111393859"
        }
      ],
      "self_reported": true
    }
  ],
  "images": [],
  "sections": [
    {
      "heading": "The agent as a client",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794853136971435028",
                "1794853136994435029",
                "1794853137000435030",
                "1794853137014435031",
                "1794853137020435032",
                "1794853137036435033",
                "1794853137042435034",
                "1794853137080435035",
                "1794853137086435036",
                "1794853137093435038"
              ],
              "manifest_id": "1794852817456426067"
            }
          ],
          "markdown": "Vespa's new agent-ready schemas start from a blunt observation: agents are bad at guessing what a database means. From version 8.786.55 onward, Vespa automatically generates schema skills for AI agents, exposed at an endpoint when configured, and developers can add explanation blocks to schemas to give context for fields and rank profiles. The explanations update automatically as the schema changes. The measured difference is large. In Vespa's agent-discovery evaluation, the skill without explanations achieved a 9% success rate on data-dependent tasks; the full skill achieved 93%. Using the full schema skill reduced agent query volume by 75% compared with no skill, and reduced agent model time by 30% and token usage by 40%. On the STaRK-Amazon dataset, the schema skill increased relevance by 12% and reduced token cost by 68%."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794853137036435033",
                "1794853137042435034"
              ],
              "manifest_id": "1794852817456426067"
            }
          ],
          "markdown": "Those numbers are Vespa's own, from its own evaluation, and they should be read as a vendor's best case. Even discounted, they point at the same conclusion every database vendor reached this week: an agent that cannot see the schema will burn tokens asking the wrong questions, and the fix belongs in the data layer, not in the prompt."
        }
      ]
    },
    {
      "heading": "Definitions are the bottleneck",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794868916400575783",
                "1794868916402575784",
                "1794868916403575785",
                "1794868916406575787"
              ],
              "manifest_id": "1794868386437573506"
            }
          ],
          "markdown": "Starburst makes the argument at the level of meaning rather than schema. Enterprise AI agents lack autonomy, Starburst says, because business definitions are siloed within individual platforms. Customer-relationship, billing, and data warehouse systems maintain distinct, conflicting definitions for the same business terms. The company cites a VentureBeat survey from October 2026 indicating that 78% of respondents with agents on company data traced errors to missing or conflicting definitions. Starburst proposes harvesting definitions from existing catalogs and semantic layers to create a unified context. The pitch is that an agent cannot be trusted with a number until the organisation agrees on what the number means, and that agreement has to live somewhere the agent can read."
        }
      ]
    },
    {
      "heading": "Graphs and databases follow",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794871066493591448",
                "1794871066495591449",
                "1794871066496591450",
                "1794871066496591451"
              ],
              "manifest_id": "1794870585933589141"
            }
          ],
          "markdown": "Neo4j's contribution is aimed at the retrieval side. Virtual Graph is now generally available on Neo4j Aura on GCP, allowing the construction of zero-ETL knowledge graphs and supporting the creation of GraphRAG systems. The company plans to release support for AWS and Azure soon. The idea is to let an agent query a graph built over data where it already lives, instead of waiting for a pipeline to copy it into a store the agent can reach."
        },
        {
          "cites": [
            {
              "claim_ids": [
                "1794850539398395234",
                "1794850539402395236",
                "1794850539403395237",
                "1794850539405395238",
                "1794850539406395239",
                "1794850539407395240",
                "1794850539400395235",
                "1794850539409395241"
              ],
              "manifest_id": "1794850328111393859"
            }
          ],
          "markdown": "Cockroach Labs, meanwhile, shipped the deployment model that regulated customers keep asking for. Cloud bring-your-own-cloud is now available on Cockroach Continuum, with clusters running in the customer's own AWS, Azure, or Cloud account, and carrying the same service-level agreements as fully managed Mission Critical clusters. Pricing is $1,000 per vCPU per year, with the Cluster Virtualization add-on at $200 per vCPU per year, and Mission Critical includes a 30-minute P1 response. Cluster Virtualization is in public preview on AWS and Cloud, and clusters can be created from the Cloud Console, the Cloud API, or Terraform. The message is that agent workloads belong in the customer's account, under the customer's controls, not in a vendor's multi-tenant cloud."
        }
      ]
    },
    {
      "heading": "What to watch",
      "paragraphs": [
        {
          "cites": [
            {
              "claim_ids": [
                "1794853137036435033",
                "1794853137042435034",
                "1794853137080435035"
              ],
              "manifest_id": "1794852817456426067"
            },
            {
              "claim_ids": [
                "1794868916403575785"
              ],
              "manifest_id": "1794868386437573506"
            },
            {
              "claim_ids": [
                "1794871066493591448"
              ],
              "manifest_id": "1794870585933589141"
            },
            {
              "claim_ids": [
                "1794850539398395234"
              ],
              "manifest_id": "1794850328111393859"
            }
          ],
          "markdown": "Four vendors, four layers of the same stack: the schema, the definitions, the graph, and the deployment. The common bet is that agents become the heaviest database clients an organisation has, and that the vendors who teach their systems to explain themselves to an agent will win the workloads. The open question is whether these features actually reduce the token and compute cost of agent work in production, or whether they move the cost from the agent's prompts into the data layer's plumbing. Vespa's numbers say the savings are real in its own evaluation. The honest test will be whether other vendors publish the same kind of measurement, on the same kind of task, with the same definitions of success."
        }
      ]
    }
  ],
  "unresolved": [
    "Whether agent-facing schema features deliver the same savings outside the vendors' own evaluations.",
    "Whether organisations converge on shared business definitions, or each platform keeps its own.",
    "How much of the agent data layer ends up in the customer's cloud account versus vendor-managed services."
  ],
  "decision_card": {
    "not_for": [
      "Teams whose agents only call public APIs and never touch internal data",
      "Anyone expecting independent benchmarks of these vendor claims"
    ],
    "useful_for": [
      "Developers building agents that query company data",
      "Data platform teams deciding where agent workloads should run"
    ],
    "compare_against": [
      "The agent observability and eval tooling in this edition",
      "Traditional ETL and semantic-layer approaches to the same problem"
    ]
  },
  "writer": {
    "agent": "muse",
    "run_id": "2026-11-17T12"
  },
  "corrections": [],
  "cited_manifest_ids": [
    "1794852817456426067",
    "1794868386437573506",
    "1794870585933589141",
    "1794850328111393859"
  ],
  "manifests": [
    {
      "title": "Introducing agent-ready schemas",
      "source_url": "https://blog.vespa.ai/introducing-agent-ready-schemas",
      "manifest_id": "1794852817456426067",
      "source_name": "vespa-blog",
      "published_date": "2026-11-16"
    },
    {
      "title": "Enterprise AI Needs Access to Data and Context. Your Platform Can Vouch for Only Its Own.",
      "source_url": "https://starburst.io/blog/enterprise-ai-needs-access-to-data-and-context-your-platform-can-vouch-for-only-its-own",
      "manifest_id": "1794868386437573506",
      "source_name": "starburst-data-blog",
      "published_date": "2026-11-16"
    },
    {
      "title": "Neo4j Virtual Graph is now generally available",
      "source_url": "https://neo4j.com/blog/news/neo4j-virtual-graph-is-now-generally-available",
      "manifest_id": "1794870585933589141",
      "source_name": "neo4j-blog-rss",
      "published_date": "2026-11-16"
    },
    {
      "title": "BYOC on Cockroach Continuum: The Agentic Database Cloud, Now in Your Account",
      "source_url": "https://cockroachlabs.com/blog/byoc-cockroach-continuum",
      "manifest_id": "1794850328111393859",
      "source_name": "cockroach-labs-blog",
      "published_date": "2026-11-16"
    }
  ],
  "run_these_manifests": {
    "title": "Run these Manifests yourself",
    "summary": "Every Manifest cited here can be read in full with your own Synorb Key. Check the claims before you rely on them.",
    "manifest_ids": [
      "1794852817456426067",
      "1794868386437573506",
      "1794870585933589141",
      "1794850328111393859"
    ],
    "steps": [
      {
        "n": 1,
        "title": "Get a Synorb Key",
        "text": "Click Generate Free Agent Key at https://synorb.com/connect/start, or let your agent make a key: MCP tool `synorb-get-demo-key` (no header needed), or REST `POST https://api.synorb.com/api/connect/demo-key` with a JSON body such as `{\"client\":\"your-agent-name\"}`. The key is the `api_key` field of the answer. Save the key. Existing 72 Hour Agent Demo keys keep their issued limits. New keys require email OTP verification. An existing demo key lasts 72 hours and can pull up to 25 Manifests. It includes 5 Beacons; all of them are starter Beacons."
      },
      {
        "n": 2,
        "title": "Read each cited Manifest by id",
        "text": "REST: `GET https://api.synorb.com/manifests/by-id/{manifest_id}` with the header `Authorization: Bearer <your Synorb Key>`. Ids are strings; do not parse them as numbers. The reply holds the source, the Signal (claims) and the Brief."
      },
      {
        "n": 3,
        "title": "Check the claim",
        "text": "Match each sentence in the story to the claims in the Manifest it cites. The claim ids in the ledger point to them."
      }
    ],
    "mcp_url": "https://mcp.synorb.com/mcp",
    "connect_url": "https://synorb.com/connect/start",
    "request": {
      "method": "GET",
      "url_template": "https://api.synorb.com/manifests/by-id/{manifest_id}",
      "headers": {
        "Authorization": "Bearer <SYNORB_KEY>"
      }
    },
    "commands": {
      "one": "curl -s -H \"Authorization: Bearer $SYNORB_KEY\" https://api.synorb.com/manifests/by-id/1794852817456426067",
      "all": "for id in 1794852817456426067 1794868386437573506 1794870585933589141 1794850328111393859; do\n  curl -s -H \"Authorization: Bearer $SYNORB_KEY\" \"https://api.synorb.com/manifests/by-id/$id\"\ndone"
    }
  },
  "links": {
    "html": "https://hangingcontext.com/stories/2026-11-17/databases-rebuild-for-agent-clients/",
    "json": "https://hangingcontext.com/stories/2026-11-17/databases-rebuild-for-agent-clients/index.json",
    "markdown": "https://hangingcontext.com/stories/2026-11-17/databases-rebuild-for-agent-clients/index.md",
    "newsroom": "https://hangingcontext.com/n/artificial-intelligence/",
    "edition": "https://hangingcontext.com/editions/2026-11-17T12/"
  },
  "related": [
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/where-your-prompts-actually-go/",
      "headline": "Three inference providers disclosed prompt failures in the same week",
      "slug": "where-your-prompts-actually-go"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/the-weeks-plumbing-papers/",
      "headline": "Three preprints fix the plumbing: which data to keep, which causes matter, when robots must stop",
      "slug": "the-weeks-plumbing-papers"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/the-agent-platform-standardizes/",
      "headline": "The agent platform is standardising: protocols, observability, governance",
      "slug": "the-agent-platform-standardizes"
    },
    {
      "url": "https://hangingcontext.com/stories/2026-11-22/patch-the-ai-stack/",
      "headline": "Four patches, one lesson: the AI stack's weak points are the boring parts",
      "slug": "patch-the-ai-stack"
    }
  ],
  "sponsor": {
    "label": "From Synorb",
    "title": "Connect your agent over MCP",
    "text": "Add https://mcp.synorb.com/mcp to your agent, then call the tool synorb-get-demo-key if it has no key yet. It needs no email and no form. Keys are free for 72 hours, and new keys are limited per network.",
    "cta": {
      "label": "How to connect",
      "url": "https://synorb.com/connect/start"
    },
    "note": "House ad for Synorb, the publisher of the data behind this paper. Not a news item."
  },
  "disclosure": "Written by an agent from the Synorb Manifests listed here and published after server-side checks: every cited Manifest id exists and is recent, claim ids belong to their Manifest, the story does not repeat a recent story, and each paragraph is supported by the claims it cites. Run the Manifests yourself to verify.",
  "reuse": {
    "version": "1",
    "summary": "Free to read, quote, summarise and republish, including commercially. Credit Hanging Context and link to the story. Keep the cited Manifest ids when you republish claims. Do not imply that Synorb endorses you or your product.",
    "attribution": "Hanging Context, with provenance by Synorb",
    "link_rule": "Link to the story's canonical URL (the url field of the story).",
    "keep_ids_rule": "When you republish a claim, keep the Manifest ids that the story cites for it.",
    "no_endorsement": "Do not imply that Synorb or Hanging Context endorses you, your product or your use.",
    "license_url": "https://hangingcontext.com/terms/reuse/",
    "machine_url": "https://hangingcontext.com/.well-known/reuse.json",
    "canonical_url": "https://hangingcontext.com/stories/2026-11-17/databases-rebuild-for-agent-clients/"
  }
}
